Rate limiting in .NET has always been an afterthought. You either bolted on AspNetCoreRateLimit (which hasn't aged gracefully), hacked together a custom ActionFilter with a ConcurrentDictionary, or shipped without any limiting and hoped nobody would hammer your endpoints. We've all been there. .NET 10's
Your 14-team Angular monolith has a 45-minute build, a 3-hour release train, and one broken import blocks everyone. I've lived this. After running micro frontends in production with Angular 22, I can tell you the situation has genuinely changed. Micro frontends have been oversold for years. Half the
Your job scheduler is probably the oldest pattern in your codebase. Hangfire or Quartz.NET, running in production, doing its thing. It works. But every time you touch the scheduling code, you wince a little. Magic strings mapping to methods. Reflection-based serialization that blows up after a rename. XML config
EF Core 11's vector search announcement was genuinely exciting, if you're on SQL Server. But according to Stack Overflow's 2024 Developer Survey, PostgreSQL is the most-used database among professional developers at 49%. Half of us watched that announcement and thought: "Cool. Doesn'
The current AI/RAG stack for .NET developers is architecturally absurd. You've got SQL Server holding your domain data, Pinecone or Qdrant sitting in a separate cloud for vectors, a sync pipeline duct-taped between them to keep embeddings consistent, and a completely different SDK with its own query
Microsoft finally killed the "which SDK do I use for agents?" problem. If you've been watching the AI agent space from the .NET sidelines, confused by AutoGen's Python-first research vibe, or frustrated that Semantic Kernel felt awkward for multi-agent scenarios, your wait is over.
You're 40 controllers deep, each with six or more actions, and your project structure looks like a filing cabinet from 1997. Or maybe you went all-in on Minimal APIs and your Program.cs has become a 600-line god file that nobody wants to touch. Either way, you'
.NET 11 Preview 5: The Features That Actually Matter Every November the .NET release train pulls into the station, and every November the "what's new" posts read like someone piped the changelog through a thesaurus. I've sat through fifteen of these cycles now. Most
Heads-up on versions: The official MCP C# SDK just went stable -- ModelContextProtocol 1.4.0 shipped in early June 2026, so we're past the preview churn. The code below targets the 1.x API. If you're reading this later, sanity-check the current package version against
I've been using GitHub Copilot since the early preview days. Inline suggestions, Chat panel, slash commands — the whole stack inside VS Code. It's a productivity multiplier. But it has always been confined to one editor window, one context, one conversation at a time. The new GitHub
If you've shipped a multi-tenant app with EF Core, you already know what I'm about to say. You get one query filter per entity. One. Want tenant isolation AND soft deletes? Mash them into the same lambda and hope nobody ever needs to turn off just
The generic entity pattern I wrote about last time is smart. But smart has a ceiling -- in high-throughput systems and AOT targets, that ceiling is lower than you think. Source generators blow past it. Where the generic pattern starts costing you To be clear: the generic entity service pattern
AI
Every project I join has the same problem. Ten entities, ten controllers, ten services, ten data access classes and all doing the exact same thing. A ProductService that's a copy-paste of CustomerService, which is a copy-paste of OrderService. Nobody questions it. It just grows. I got fed up
AI
I want Gemini in my .NET API without a dependency on whichever SDK is flavour of the month. The official Google .NET SDK targets net8.0/netstandard2.0 and its multimodal API is still in flux. A typed HttpClient, System.Net.Http.Json, and 80 lines of C# gets you
AI
Copilot Without Context Is a Fast Way to Generate Tech Debt Out of the box, Copilot defaults to the patterns it was trained most heavily on: controllers, [ApiController], IActionResult, DbContext calls direct in endpoints. That is Microsoft tutorial code. It is not production architecture. The suggestions are fluent and fast.
AI
The third time Claude Code suggested I scaffold a controller, I stopped typing and started writing a CLAUDE.md file. That's the problem with AI coding assistants without context: they default to whatever Microsoft's documentation says. Ask Claude to add a new entity and it reaches
AI
Every time I paste a snippet into ChatGPT or Claude, I'm sending proprietary code to a third-party server. That's a non-starter for client work. Add the per-token costs once your usage scales, and the internet dependency when you're travelling — or just in a hotel
AI
77.2% on SWE-bench Verified. A 27B open-weight model. That number sat with me for a while when I first saw it, because Claude Opus 4.6 — the current best-in-class closed model for coding — scores 80.8%. We're talking about a 3.6-point gap between a model you
The last time I hand-wrote a GitHub Actions YAML file for a multi-service .NET deployment, I lost four hours to indentation errors and secret-binding typos. Four hours. Not shipping features. Not fixing bugs. Arguing with a text file about whitespace. That was eight months ago. I haven't touched