Foreword by Simon Brown
My aspiration to become a software architect stemmed from my interest in the technical side of software design. I really enjoy discussions about how we can best use technology to solve a problem, and how to create codebases that are highly modular, well-structured, and easy to work with.
What nobody tells you though, is that these technical aspects are just one part of the architecture puzzle. It’s not just about technology and designing software. It’s about designing software and solving problems within a specific organizational context, and being aware of what’s happening around you, so that you can successfully navigate and influence that context where necessary. It’s crucial, therefore, that architects realize they need to communicate and influence at different levels, with different audiences, both inside and outside of their immediate team environment.
As an industry, however, we do a relatively poor job teaching software developers how to move into software architecture roles, let alone providing help for those who are currently in such a role. This is especially true for the nontechnical aspects. A quick browse of your favorite bookstore will reveal a plethora of books about software architecture, architectural styles, architectural patterns, DevOps, automation, enterprise architecture, Lean, Agile, and so on. You’ll find far fewer books related to people and communication. And it’s even rarer to find a single book that covers all of these topics. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access