When to optimize, when to wait
Distributed systems fail in ways that are hard to predict. After years of debugging production incidents, certain patterns keep recurring. This post explores a few.
Latest posts
- Simplicity as a selling point· 39 minutes ago · 24,774 reads
- On API design principles· 37 minutes ago
- Notes on system reliability· 13 days ago
On writing code that lasts
Naming is one of the hardest problems in software, yet we spend less time on it than we should. Let's talk about why it matters and how to get better at it.
From the archive
Performance optimization is a tempting distraction. Every line of code that exists to optimize one specific case is a line that must be maintained and understood forever.
About this site
A technical writer exploring systems thinking, code design, and the intersection of tools and thought.
Thoughts on code. Updated weekly.
Elsewhere
Occasional thoughts on technical topics. Past essays here.