I write about ASP.NET Core, AWS, APIs, testing, infrastructure, and developer tooling, grounded in problems I encounter while building real systems.
Contract-first API design is less about writing YAML first and more about making a shared boundary explicit before implementation decisions harden. This post looks at why that matters when one service is consumed by several independently...
AI helped me publish far more frequently by removing friction from how I develop and refine ideas, while keeping the filters, structure, and review that determine whether a post is worth publishing.
A unit test should show what makes its scenario special. AutoFixture can provide a valid context by default so the Arrange phase only needs to describe the difference.
Keep Refit clients focused by responsibility while exposing one convenient dependency to the rest of the application.
A small publishing automation started with Jekyll’s stateless builds and somehow ended with a generic event routing runtime.
Paying for OSS is not a betrayal of its ideals. The harder problem is funding future maintenance without rewriting the promise attached to what was already given away.
Build, test, version, package, and securely publish a .NET library to NuGet.org using GitHub Actions, MinVer, workflow artifacts, and trusted publishing.
Add strongly typed defaults to the .NET configuration pipeline while keeping the normal precedence and override behavior of other configuration providers.
Source generation can register injectable Minimal API endpoint classes and map their routes without runtime scanning or manual composition.
Switching to Native AOT shouldn’t change how you write your business logic. It should change how the Lambda is hosted, built and serialized around it.