About
I’m Matt, a software engineer focused on building systems that are clear, resilient, and boring in the right ways.
I spend most of my time thinking about cloud architecture, distributed systems, and developer tooling. I enjoy problems where structure actually matters: designing APIs that age well, building predictable infrastructure, and creating workflows that help teams move without friction.
This site is intentionally small and opinionated.
This site
This blog is my digital garden: a place to document what I’m learning, sketch ideas in public, and keep notes on things I want to understand more deeply.
Some posts will be polished, whilst others are half-formed. That’s deliberate. I treat this space as somewhere between a notebook and a reference, rather than a feed or a portfolio.
If something here is useful to someone else, that’s a bonus.
What I mean by “digital garden”
When I refer to this site as a digital garden, I don’t mean an unstructured collection of notes. I mean a long-lived body of writing that evolves over time, where ideas are revisited, refined, and occasionally pruned.
I use the term “garden” deliberately: the same pruning, cleanup, and ongoing care apply to software systems as much as they do to writing.
Posts may be updated, extended, or linked together as understanding deepens. Stability comes from structure and validation, not from treating content as immutable.
Elsewhere
You can find code and experiments on GitHub(opens in a new tab), connect with me on LinkedIn(opens in a new tab), or follow along via the RSS feed if you prefer quieter updates.