
100 Lessons Every Solution Architect Should Learn
A career's worth of hard-won lessons on how great architects actually think, decide and lead. ~220 pages, illustrated.
Architecture was never about the technology. Essays and books on the part of the job that doesn't go out of date — how great architects actually think, decide and lead.
Every architecture job advert describes the tools and forgets the purpose. That gap is why the role has never had a clear definition.
For years the honest answer to "what is an architect" would have been a technical one. Here is the definition that replaced it, and what it quietly explains.
Every component in a system can be individually excellent, and the system can still fail. That gap between local and global optimisation is what architecture is for.
"What's the right architecture?" is the wrong question. Architecture is never judged on whether you guessed the best option — only on whether your reasoning survives pressure.
The argument in the essays, worked out in full.

A career's worth of hard-won lessons on how great architects actually think, decide and lead. ~220 pages, illustrated.

Three classic design problems across Azure, AWS and Google Cloud, each ending in a design-review simulator.

A short, sharp manifesto: architecture was never about the technology. The entry point to the series.
Occasional essays on the craft of architecture — the judgement, not the tools. No spam; unsubscribe anytime.
Signup activates once the email provider is connected.