🪵 There’s a woodpecker on the cover of Software Architecture: The Hard Parts. Probably a coincidence – O’Reilly doesn’t pick cover animals to match the topic. But I like to imagine it’s a particularly determined one drilling into the same hard spot, over and over, until something gives – which is what got me thinking about a habit chess players deliberately train that architects rarely practice in a structured way.
♟️ Chess has a training trick called the Woodpecker Method. You solve a batch of puzzles, then solve the exact same batch again – faster. Then again. Not to memorize answers, but to stop reconstructing them from scratch. A pin is a pin whether it happens on move 12 or move 40. After enough reps, you don’t calculate everything; you just see where to look.
Architecture doesn’t work like that: there’s no answer key. Two good architects can look at the same trade-off and land on different, defensible paths. The “puzzle” also doesn’t hold still – come back to a decision a year later and half the constraints have changed. So the chess training trick doesn’t work the same way in architecture.
🔁 But the idea underneath it does. We don’t build better judgment by collecting more one-off decisions. We build it by revisiting similar trade-offs until we start noticing the patterns underneath them.
Here’s the catch: if you only ever revisit two or three decisions, you’re not learning patterns – you’re just remembering stories. That’s déjà vu, not recognition. Even the authors say as much: trade-off playbooks aren’t built in one sitting, they’re built over time, through iteration.
🧭 A practical routine I like to try:
- Keep a running list of real trade-offs as you make them
- Every few months, pick 3–5 and re-decide them cold, before looking at what you actually chose
- Compare: What would I pick today? What did I expect to happen? What actually happened?
- Borrow a second opinion: ask someone who wasn’t in the room and compare their reasoning to the operational outcome
The goal isn’t to prove your past self right. It’s to discover what your past self missed.
Maybe the woodpecker on the cover is just decoration. Or maybe it’s a reminder that expertise is built by returning to the same hard parts again and again – not to memorize answers, but to uncover the patterns beneath them. The best architects recognize the shape of the problem before they start solving it.
💬 Which architectural trade-off still surprises you when you look back at it?