37 Things One Architect Knows

37 Things One Architect Knows compiles hard-earned lessons from enterprise architect Gregor Hohpe's career at major tech companies. The book presents these insights through a collection of patterns, antipatterns, and real-world experiences that define what it means to be an effective architect. Each chapter focuses on a specific aspect of the architect's role, from technical leadership and communication to organizational dynamics and project delivery. The format allows readers to consume the material in any order, with each "thing" standing as its own self-contained lesson while connecting to broader themes. The content draws heavily from Hohpe's work at Google, integration projects at multiple Fortune 500 companies, and his consulting experience across industries. His observations cover both the technical and human elements of architecture work. The book serves as a guide for navigating the transition from developer to architect, highlighting the shift in mindset and responsibilities required for the role. It presents architecture as a practice that extends beyond technical decisions into leadership, strategy, and organizational change.

Readers find the book provides practical guidance for architects transitioning into leadership roles. The pragmatic tone and focus on real-world scenarios resonates with experienced architects. What readers liked: - Clear discussions of organizational politics and stakeholder management - Strong emphasis on communication skills over technical details - Relatable stories from author's experience - Balanced perspective on technical and non-technical aspects What readers disliked: - Some felt sections could be more concise - Limited code examples and technical depth - Cost ($37) seen as high by some readers - A few wanted more concrete architectural patterns Ratings: Goodreads: 4.1/5 (126 ratings) Amazon: 4.5/5 (32 ratings) Notable reader comment: "Finally a book that talks about the real challenges architects face - managing relationships and influencing decisions - rather than just patterns and diagrams." - Goodreads review [Note: Limited review data available online as this is primarily sold as an ebook through author's website]

The Software Architect Elevator by Gregor Hohpe Presents the role of software architects through real-world experiences of connecting technical decisions to business outcomes.

Just Enough Software Architecture by George Fairbanks Maps the practical path between theory and practice in software architecture through risk-driven approaches.

Software Architecture in Practice by Len Bass, Paul Clements, Rick Kazman Connects architectural decisions to business goals using concrete case studies and established patterns.

The Art of Scalability by Martin L. Abbott, Michael T. Fisher Examines architectural scaling patterns through organizational, technical, and process models drawn from enterprise implementations.

Technology Strategy Patterns by Eben Hewitt Bridges technical architecture and business strategy through patterns derived from Fortune-500 company experiences.

🏗️ Gregor Hohpe worked as the Chief Architect at Allianz, one of the world's largest insurance companies, where he guided many of the insights shared in the book. 📚 The book's unique format presents each concept as a distinct "thing," making it easy for readers to digest complex architectural principles in standalone segments. 💡 The author coined the term "Architect Elevator," describing how enterprise architects must move between the executive penthouse and the IT engine room to be effective. 🔄 Many of the book's patterns and principles were first developed through the author's blog, "The Architect Elevator," which attracted a significant following in the tech community. 🌐 Despite focusing on software architecture, the book draws parallels from traditional building architecture, demonstrating how centuries-old design principles still apply to modern technology systems.