Creating this blog
Articles about how I built this website with Jekyll, GitHub Pages, Dev Containers, and the tools around it.
6 articlesExplore the blog
Practical notes from building real systems, from 2020 to today.
Topics
Explore a few areas of the blog, each with an introduction and related articles.
Articles about how I built this website with Jekyll, GitHub Pages, Dev Containers, and the tools around it.
6 articlesPractical approaches to testing ASP.NET Core applications at different boundaries, from individual handlers to fully hosted applications with authentication, databases, and gRPC.
5 articlesPractical patterns for using AutoFixture to keep .NET tests focused, reduce incidental setup, and customize test data when the scenario requires it.
3 articlesPractical approaches to structuring, authoring and observing .NET AWS Lambda functions, from the programming model and event-source handling to OpenTelemetry and Native AOT.
6 articlesPractical approaches to designing, organizing, testing, and generating ASP.NET Core Minimal APIs, including source generation and OpenAPI-driven contracts.
5 articlesAI is taking over some of the work that helped previous generations of software engineers develop their judgment. If those opportunities diminish, how will today’s juniors become tomorrow’s seniors?
After years of writing C#, there are still language features I wish existed. From simpler generic APIs to richer enums and more expressive types, here’s my personal wishlist, grounded in problems I’ve encountered while writing real code.
An MCP server, a secure tunnel, and a personal access token. What could go wrong? A Halloween horror story about shadow IT and security.
AI doesn’t just make writing code cheaper. It can also make architectural exploration cheaper, letting us investigate questions we previously wouldn’t have had time to pursue.
Managing roughly 25 GitHub repositories was becoming a maintenance problem. Here’s how a growing script turned into Octosmith, a declarative tool for aligning repository configuration without requiring uniformity.
Early-career developers can easily mistake short-term productivity for progress. Growing into a senior also requires context, relationships, judgment, and exposure to how experienced engineers think.
AutoFixture composes the test context. Bogus makes generated data easier to describe.
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.