Appendix A. Leftovers: The Top Six Topics We Didn’t Cover


There’s a lot more to be said about software architecture. We promise, you’re done with this book. But reading this book is just the first step in your journey to thinking architecturally, and we couldn’t in good conscience let you go without a little more preparation. So, we’ve gathered a few additional juicy bits into this appendix. Each of the topics that follow deserves as much attention as the other topics we’ve covered. However, our goal here is just to give you a high-level idea of what they’re all about. And yes, this really is the end of the book. Except for the index, of course—it’s a real page-turner!


#1 The coding architect

Yes! We firmly believe that software architects should still write source code. Not only does it help you maintain your technical skills, but it also shows you how your architectural decisions play out in real life.

However, it’s not always easy to balance hands-on coding with software architecture. As you’ve seen, there’s a lot to software architecture. It will take up most (if not all) of your time.

Don’t worry though—we’ll share some tips and techniques for writing software while being an effective software architect.

Don’t become a bottleneck

Be careful not to take ownership ...

Get Head First Software Architecture now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.