Versioning stays invisible right up to the point when it fails. A package has to be reissued, a support case depends on one exact binary, or staging and production turn out to run artifacts from the same commit that do not quite match. At that moment the version number stops being release-note decoration and becomes engineering data.
Read Blog Post
Distributed applications tend to feel straightforward until a real cloud dependency enters the picture. Azure Cosmos DB is a good example. In Azure, the preferred model is usually clear: the application should connect without secrets and authenticate through Managed Identity. Local development has different constraints. There is no managed identity attached to a machine in the same way, but the application still needs a reachable endpoint, credentials, startup ordering and a database that exists before the first request reaches repository code.
Read Blog Post
MiMo V2.5 is the latest reasoning and coding model from Xiaomi’s AI lab. Xiaomi positions MiMo as a general-purpose reasoning model with particular strength in code generation, structured output and tool calling. In May 2026 the model was made available through OpenCode Zen as part of a promotional offer, meaning it can be used at no cost during the promotion period.
Read Blog Post
GitHub Copilot’s pricing shift from flat premium request units to token-based GitHub AI Credits, scheduled for June 1, 2026, changes the economics of heavy AI usage in VS Code meaningfully. Models with large context windows, high output verbosity or intensive agent loops now have a more direct relationship between compute and cost. That makes model selection a more relevant engineering decision than it was under the older quota model.
Read Blog Post
GitHub Copilot is moving into a different cost model. GitHub announced that Copilot plans will transition from premium request units to GitHub AI Credits on June 1, 2026. Usage will be calculated from token consumption, including input, output and cached tokens, using the listed API rates for each model. This is a more direct mapping between compute usage and billing, but it also changes the economics for teams that have started to use agentic workflows heavily.
Read Blog Post
Frontend development often hits a practical wall early: the backend API does not exist yet, is unreachable in local environments, or is shared between multiple teams and cannot be safely modified during development. The typical workarounds - hardcoded response stubs, in-memory interceptors, or hand-rolled Express servers - all impose overhead that does not belong in the development workflow.
Read Blog Post
Cloudflare Workers can separate production and preview traffic cleanly without sacrificing canonical URL control. For search visibility, that detail matters more than the mere existence of preview links. The production hostname stays singular, the preview hostname stays disposable, and the Worker runtime can normalize HTML paths before duplicate URLs leak into indexing.
Read Blog Post
Azure Static Web Apps has one feature that is easy to underestimate until a team starts using it seriously: pull requests can behave like first-class deployment units.
Read Blog Post
GitHub is an operational platform, not a backup strategy. For a long time, that distinction often felt theoretical because GitHub is - usually - highly available and because Git itself already distributes history well. The gap becomes visible once repositories are treated as regulated business assets instead of convenient hosting locations.
Read Blog Post
Testing in .NET has historically been associated with VSTest. That choice was reasonable for a long time because VSTest offered broad tooling support, deep IDE integration and a familiar execution model for MSTest, xUnit and NUnit projects. But the .NET ecosystem has changed. Native AOT, trimming, simplified deployment models, executable-first workflows and more explicit build-time configuration have pushed the platform toward models that do not fit particularly well with the older test infrastructure.
Read Blog Post
GitHub Copilot custom agents allow teams to define specialized AI assistants, each with its own role, tool access and behavioral boundaries. Instead of relying on one general-purpose assistant for everything, a team can create multiple agents that mirror the actual roles in the engineering organization. After working with custom agents for a while, the biggest insight was simple: the quality of AI-assisted engineering improves dramatically once the AI knows what role it is supposed to play.
Read Blog Post
Publishing NuGet packages has traditionally required one uncomfortable compromise: a long-lived API key had to exist somewhere in the delivery pipeline. Even when that secret was stored in a secure CI system, the model still relied on a credential that could be leaked, copied, mis-scoped or forgotten. Once exposed, that key could often be reused until someone noticed the incident and rotated it.
Read Blog Post
After many years of workarounds, design discussions and library-level substitutes, unions are finally becoming a first-class part of C#. The proposal in the C# language repository is no longer a distant idea. With the feature now appearing in the .NET 11 preview train as an early C# 15 capability, the direction is concrete enough to discuss in practical terms.
Read Blog Post
C# is a powerful language, but there is one road it has not yet fully paved: native discriminated union types. Developers have been working around this absence for years, typically choosing between throwing exceptions for non-exceptional paths, returning nullable values, using out parameters or layering custom wrapper classes on top of every service boundary. Each of these approaches carries a cost - in clarity, type safety or runtime efficiency.
When building cloud-native .NET applications, two goals often matter at the same time: a fast local development loop and a clean path to real Azure resources for publish mode. .NET Aspire with Azure Cosmos DB supports exactly this pattern.
Read Blog Post
The .NET team just released the first preview of .NET 11 and there is already a lot to talk about. While this is an early preview - not a release candidate - the breadth of changes touching the runtime, libraries, ASP.NET Core, Blazor, C#, the SDK and Entity Framework Core gives a clear picture of where the platform is heading. Let me walk you through the most important changes you should know about.
Read Blog Post
Large language model agents can appear intelligent while still producing unstable output across runs, contexts and tasks. In practice, this instability is rarely caused by model quality alone. The dominant factor is often missing operational structure: no explicit boundaries, no role-specific constraints, no reusable task patterns and no agreed execution policy.
Read Blog Post
Local SQL Server database files provide a pragmatic way to keep a real SQL Server engine close to the application without provisioning a full server. A LocalDB database lives in a single .mdf file (plus a log file), runs in user mode and behaves like SQL Server for most application scenarios. That makes it a strong fit for local development, integration tests and tooling that needs relational features without the overhead of infrastructure setup.
Read Blog Post
The landscape of AI development is shifting rapidly from simple chat interfaces to fully integrated, agentic workflows like the Ralph Loop . GitHub has recently introduced the GitHub Copilot SDK , a powerful toolkit that allows developers to programmatically harness the engine behind the GitHub Copilot CLI.
Read Blog Post
What if an AI agent could write code, run tests, fix errors and repeat this process autonomously until the job is done? The Ralph Wiggum Method makes this possible with a simple but powerful loop pattern. Named after the lovable Simpsons character, it embodies the philosophy: persistence wins over perfection.
Read Blog Post