After two years of writing, rewriting, and iterating, Developer to Architect is available today on LeanPub at leanpub.com/devtoarch. This post explains what is in the book, who it is for, and why I wrote it the way I did.
Why this book exists
I have spent more than two decades working as a software architect. In that time, I have watched talented developers step into architecture roles and struggle, not because they lacked technical ability, but because nobody told them what the role actually requires.
The technical literature on software architecture is excellent. There are rigorous books on architectural patterns, distributed systems, and the hard parts of architectural decision-making. But almost none of them address the transition itself: the shift in orientation from building things to defining what should be built, from solving problems to framing them, from being a technical expert to being an organizational force.
Developer to Architect is the book I wished had existed when I made that transition. It addresses every dimension of the architect's role, technical and human, in a single guide.
What is in the book
The book is structured in six parts:
- Part I: The Mindset Shift. Three chapters on the core cognitive change required: what architects actually do, the shift from solving problems to defining them, and how to think in systems.
- Part II: Technical Foundations. Ten chapters covering the technical domains an architect must understand deeply: distributed systems, data architecture, APIs, scalability, security, compliance, observability, AI, and cloud.
- Part III: The Craft of Design. Five chapters on the practice of architectural work: making decisions, using patterns, modernizing legacy systems, drawing diagrams that communicate, and balancing quality attributes.
- Part IV: Architecture Across the Organization. Three chapters on governance, reference architecture, and communication as the architect's primary tool.
- Part V: The Human Side. Three chapters on leading teams without authority, navigating stakeholder politics, and managing trade-offs under pressure.
- Part VI: The Career Transition. Four chapters on closing the skills gap, navigating the transition inside your company, the first ninety days, and what comes next.
The book also includes nine appendices covering ADR templates, architecture review checklists, skills self-assessments, diagramming tools, recommended reading, DORA metrics, quality attributes, certifications, and companion site resources.
Who it is for
The primary audience is senior software engineers and lead developers who are preparing to move into architecture roles. These are people with strong technical foundations who need guidance on the organizational, communication, and strategic dimensions of architectural work.
The book is also useful for developers who have recently moved into architecture roles and are navigating the early stages of the transition. And for engineering managers who want a resource they can recommend to high-potential engineers on a path to architecture.
It is not a patterns catalog. If you want an in-depth treatment of microservices decomposition or distributed system patterns, there are excellent books for that. This book is the companion to those books: it covers the career, the role, and the person, not just the technical vocabulary.
Free companion resources
The companion site at devtoarch.com/resources includes ten downloadable templates and worksheets referenced throughout the book: ADR templates, architecture review checklists, quality attribute worksheets, stakeholder mapping templates, a 90-day architect plan, and more. All free.
Get the book
Developer to Architect is available now on LeanPub in PDF and ePub formats. LeanPub's minimum price is $19.99 and the suggested price is $39.99. You can pay what the book is worth to you. All readers get free updates for life.