I've built a lot of infrastructure and got plenty of it wrong. Most of what I know came from repairing those mistakes.

I write about infrastructure decisions that are easy to hand-wave and hard to live with later: defaults, boundaries, contracts, review paths, failure modes.

The technical posts stay deep in the work. The broader point is why infrastructure choices keep their shape long after the first implementation.