Essays on software engineering, design systems, and the craft of shipping things. Written when I have something worth saying.
The teams who write the cleanest code rarely build the most resilient systems. Here's why I've stopped optimizing for elegance and started optimizing for the person who'll inherit this codebase three years from now.
Read the essay
Why I optimize for the next maintainer, not the cleverest abstraction.
Most type scales are math. The ones that feel right are also taste.
Scope creep isn't a contract problem — it's a conversation problem.
Three layers, four invalidation rules, and why most teams skip step zero.
A pragmatic taxonomy for accent, surface, and text — across themes.
Abstractions have a half-life. Here's how I decide when to extract.
Five questions I ask myself every December — and why three of them changed.
The honest checklist I run before reaching for Redis, ClickHouse, or Kafka.
Six books, two of which had nothing to do with software.
No posts in this category yet — check back soon.
I take reader questions seriously — half the essays here started as someone's email.
