The Software Architect Elevator

I don’t think it’s necessary to introduce Gregor Hohpe. I’m a big fan, having read Enterprise Integration Patterns, and I’ve recommended the book ever since. When I spoke at the Software Architecture Gathering in 2024, I was fortunate enough to meet him and purchase this book. I’m the happy owner of a signed copy. Modern architects don’t try to be the smartest people in the room–they make everyone else smarter.

This review is about The Software Architect Elevator by Gregor Hohpe from O'Reilly.

I don’t think it’s necessary to introduce Gregor Hohpe. I’m a big fan, having read Enterprise Integration Patterns, and I’ve recommended the book ever since. When I spoke at the Software Architecture Gathering in 2024, I was fortunate enough to meet him and purchase this book. I’m the happy owner of a signed copy.

Modern architects don’t try to be the smartest people in the room–they make everyone else smarter. They ride the Architect Elevator from the penthouse, where the business strategy is set, to the engine room, where the enabling technologies are implemented. They shun popular buzzwords in favor of decision discipline and clear communication across levels.

Facts

Chapters

  1. Architects
    1. The Architect Elevator
    2. Movie-Star Architects
    3. Architects Live in the First Derivative
    4. Enterprise Architect or Architect in the Enterprise?
    5. An Architect Stands on Three Legs
    6. Making Decisions
    7. Question Everything
  2. Architecture
    1. Is This Architecture?
    2. Architecture Is Selling Options
    3. Every System Is Perfect…
    4. Code Fear Not!
    5. If You Never Kill Anything, You Will Live Among Zombies
    6. Never Send a Human to Do a Machine’s Job
    7. If Software Eats the World, Better Use Version Control!
    8. A4 Paper Doesn’t Stifle Creativity
    9. The IT World Is Flat
    10. Your Coffee Shop Doesn’t Use Two-Phase Commit
  3. Communication
    1. Explaining Stuff
    2. Show the Kids the Pirate Ship!
    3. Writing for Busy People
    4. Emphasis Over Completeness
    5. Diagram-Driven Design
    6. Drawing the Line
    7. Sketching Bank Robbers
    8. Software Is Collaboration
  4. Organizations
    1. Reverse-Engineering Organizations
    2. Control Is an Illusion
    3. They Don’t Build 'Em Quite Like That Anymore
    4. Black Markets Are Not Efficient
    5. Scaling an Organization
    6. Slow Chaos Is Not Order
    7. Governance Through Inception
  5. Transformation
    1. No Pain, No Change!
    2. Leading Change
    3. Economies of Speed
    4. The Infinite Loop
    5. You Can’t Fake IT
    6. Money Can’t Buy Love
    7. Who Likes Standing in Line?
    8. Thinking in Four Dimensions
  6. Epilogue: Architecting IT Transformation
    1. All I Have to Offer Is the Truth

Pros and cons

You might have noticed that there are lots of chapters. Yet, the book isn’t "big". Thus, each chapter is between 5 and 10 pages. To me, it’s a big plus: I can focus much better on a small chapter before going to sleep than to slice a chapter between multiple sessions or increase my reading span.

The author speaks from experience. Many sections in the book spoke to me, as something I had experienced in my professional life. Think "experience distilled" in a book.

If you are into technical stuff, you’ll be disappointed. The book is strictly about organization-related matters. On this side, it’s a trove of wise advice.

The book is segmented into chapters, but I think they can be read in any order, as each is cohesive enough. Early chapters tend to reference later chapters less than the opposite. That might be the only reason for the sequence.

The book’s advice, just like any other, can’t be applied blindly. Experience is hard to transmit as it is. You need to carefully read each advice multiple times, analyze its context, evaluate your context, try to apply it, then measure. Rinse and repeat. Yes, organizational matters are more complex to handle than technical ones.

While the subject is serious and the anecdotes relevant, the tone is humorous. Some might like it, some might not. I belong to the former crowd.

Conclusion

If you already have a couple of years of experience and feel your technical skills aren’t enough, I’d definitely recommend this book.