March 21, 2026
Thinking About System Design Differently
Most system design discussions focus on scale. But what if we started with simplicity instead?
Every system design discussion I’ve been in starts the same way: “How do we handle millions of users?”
But here’s the thing — most systems don’t have millions of users. And designing for scale you don’t have yet is one of the most expensive mistakes you can make.
Start Simple
The best architecture is the one you can understand in five minutes:
- A single database
- A monolithic application
- A straightforward deployment pipeline
You can always add complexity later. You can’t easily remove it.
When to Scale
Scale when you have evidence, not anxiety:
- Measure first — Use metrics to identify actual bottlenecks
- Scale the bottleneck — Don’t redesign the whole system
- Keep it boring — Proven technologies beat shiny ones
The Real Skill
The real skill in system design isn’t knowing how to build a distributed system. It’s knowing when not to.
Senior engineers aren’t the ones who add complexity. They’re the ones who fight it.