Notes

I spent two years arguing for splitting our repo. The boundary I was protecting was social, not technical — tooling caught up faster than my opinions did.

• practices
• tooling

A field guide to EXPLAIN (ANALYZE, BUFFERS): what the planner tells you, where row estimates go wrong, and the three rewrites that fix most slow queries.

• databases
• performance

Small, reversible, observable. The most senior thing on my last team wasn't a system — it was that nobody felt anything when we shipped.

• operations

"Make illegal states unrepresentable" sounds like a slogan until a union type deletes a whole class of bug. Three before/afters from a real codebase.

• typescript
• practices

What changed when we treated pages as a budget we owed the team back: tighter alerts, real follow-the-sun, and a blameless review that people stopped dreading.

• teams
• operations

Coverage is a map, not the territory. Where I now spend the testing budget instead — and the one number I still watch closely.

• testing