Editor's note
I pulled together a mixed issue again: AI agents, authentication, caching, architecture, and a bit of clean-code philosophy. The distributed locks piece and the duplicate-orders war story stood out to me because they get past theory and into the messy parts teams actually ship. I also liked the Blazor cross-platform post for showing how far one codebase can go without resorting to a forest of #if directives.
AI agents, auth, caching, and clean code
Enjoying the newsletter? Your feedback helps us grow and reach more developers.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
Clean C# Code: Best Practices, Smart Patterns & Real-World Examples in .NET Core
A solid reminder that “works on my machine” is not a production strategy.
Building AI Agents with .NET & AutoGen in 2026
AI agents, MCP, and chatbot guidance show how quickly the .NET AI stack is maturing.
ASP.NET Core + JWT + OAuth 2.0 — Authentication Done Right in 2026
JWT, OAuth, and DI are evergreen topics when teams need secure, maintainable APIs.
Generative AI for Beginners in .NET 10: From Curiosity to Real Applications
The distributed-locks article and duplicate-orders story are the kind of operational lessons worth sharing.
I Added Resilience to My .NET App. It Started Sending Duplicate Orders.
Blazor without platform-specific conditionals is the sort of practical engineering win I like to see.











