I write about the parts of software nobody demos
I'm a backend engineer working mostly in C#, Angular and Azure. Most of what I publish here started as a decision I had to defend to a team, so the posts lean toward trade-offs rather than tutorials.
What I work on
Ten years on line-of-business systems: order pipelines, integrations that had to keep running while the vendor changed their API, and a few migrations that went better than expected. Currently focused on modular monoliths and on making async boundaries explicit instead of accidental.
I care about code that a new joiner can read on their first afternoon. That usually means fewer abstractions than the pattern books suggest, and better names than I managed the first time.
Everything here is my own opinion, written on my own time. Code samples are simplified but taken from things that actually shipped.
Topics I keep coming back to
Architecture
Boundaries, slices, and when a monolith is the right answer.
API Design
Contracts, versioning, and being kind to the client team.
Design Patterns
Which ones earn their keep in a real codebase.
Azure
Functions, queues, and the cost of getting it slightly wrong.
Timeline
Elsewhere
Get new posts
One post a fortnight. Unsubscribe any time.