The case against premature abstraction
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.
Recent writing
- Lessons from legacy codebases · 51 minutes ago · 47,129 reads
- Notes on system reliability · 22 hours ago
- Design debt we never talk about · 12 hours ago
Patterns in distributed systems
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
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
Occasional thoughts on engineering practices, tooling, and how we think about code. No sponsors, no tracking, no ads.
Thoughts on craft. Updated sporadically.
Elsewhere
Occasional thoughts on design topics. Past essays here.