Home Archive Issue #444
Issue #444

JSON choices, API reliability, and C# internals

Covers Newtonsoft vs System.Text.Json, ASP.NET Core error handling, Azure DevOps CI, Cosmos DB cost tuning, and core C# design tradeoffs.

Jasen's top three picks

  1. 1
    Newtonsoft.Json vs System.Text.Json Which Should You Use in .NET?

    medium.com

    A solid practical comparison of the two JSON stacks, especially if you're balancing legacy compatibility against newer platform defaults and performance.

  2. 2
    Beyond the Wizard: Why Modernization Chat is the New Standard for .NET Upgrades

    medium.com

    Modernization is less about running a wizard now and more about guided decision-making, which is the interesting shift this piece highlights.

  3. 3
    Claude Code: Two-Agent Workflow

    blog.stackademic.com

    The architect-developer split is a familiar pattern, and the article frames it as an AI-assisted workflow for microservice implementation.

Editor's note

I put together another intentionally mixed issue here, with a few practical pieces that should age well. The Newtonsoft.Json vs System.Text.Json comparison is useful because that choice still affects compatibility and performance, and the ASP.NET Core global error handling article is the kind of fundamentals work teams benefit from immediately. I also liked the Cosmos DB cost guidance since AI-flavored workloads can amplify bad data-layer assumptions fast.

Today's articles

Related issues

📬 Get daily .NET content delivered to your inbox