Editor's note
I kept this issue intentionally mixed: database performance, language features, architecture, and tooling all made the cut. The EF Core plan cache article is a good reminder that “working” queries can still hurt you at scale, and the GitHub Actions runner CPU piece is a practical win for anyone paying for CI time. I also liked the C# 14 and .NET 10 posts because they show where the platform is headed without losing sight of day-to-day code quality.
EF Core, C# 14, and GitHub Actions
Enjoying the newsletter? Your feedback helps us grow and reach more developers.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
EF Core, Ad-Hoc Queries, and Plan Cache Pollution
Hidden EF Core costs show up in places many teams never inspect.
Understanding SQL and NoSQL Distributed Transaction Problem in C# — Transactional Outbox Pattern
A practical transactional outbox refresher for mixed SQL and NoSQL systems.
Partial Events and Constructors in C# 14 (.NET 10) Explained with Examples
C# 14 and .NET 10 keep pushing both ergonomics and speed forward.
Channels in C# .NET: Building High-Performance Concurrent Pipelines
Channels remains one of the best tools for serious concurrent pipelines.
Migrating from CRUD to CQRS and Event-Sourcing with Akka.Persistence
A useful reminder that GitHub Actions runners can waste CPU even when idle.










