On writing code that lasts
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.
Recent posts
- Patterns in distributed systems · 19 hours ago · 5,445 reads
- Notes on system reliability · 50 minutes ago
- When to optimize, when to wait · 38 minutes 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
Most codebases grow in directions their authors never anticipated. The pressure to optimize early is real, but constraints often produce more elegant solutions than freedom ever could.
About this site
Occasional thoughts on engineering practices, tooling, and how we think about code. No sponsors, no tracking, no ads.
Thoughts on design. Updated sporadically.
Elsewhere
Occasional writing on systems topics. Archives here.