On writing code that lasts
The tools we reach for shape our thinking. I've spent the last decade in terminals and shells, and it's changed how I approach problem-solving in subtle ways.
Recent posts
- When to optimize, when to wait · 19 days ago · 4,958 reads
- Incremental adoption of types · 49 minutes ago
- Rethinking notification design · 53 minutes ago
Lessons from legacy codebases
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.
From the archive
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.
About this site
A technical writer exploring systems thinking, code design, and the intersection of tools and thought.
Thoughts on design. Updated monthly.
Elsewhere
Occasional writing on systems topics. Archives here.