Why I started writing

I've been doing DevOps and Platform Engineering work for years. Most of what I've learned, I learned by doing — and a lot of the specific, useful knowledge is scattered across Slack threads, internal wikis, and conversations that never made it anywhere public.

This is where that changes.

Most of what lands here will be narrow. Not broad overviews — there are enough of those — but the things I wish existed when I was solving a specific problem: the precise reason a Kubernetes cluster was costing 3x more than it needed to, the exact step that breaks CI/CD pipelines when you move to OIDC, the non-obvious consequence of a cost optimisation that looks good in a dashboard but moves the problem somewhere harder to see.

Narrow, specific, useful. That's the plan.

One exception, stated up front so it does not look like a contradiction later: the long teaching guides tagged guide are deliberately broad. They come out of a DevOps course I teach, they start from first principles on purpose, and they are written for a different reader than everything else here.

If you have a specific problem you'd like me to write about, send me a message.