![97 Things Every Software Architect Should Know [Repost]](https://pixhost.icu/avaxhome/c0/17/002417c0_medium.jpeg)
97 Things Every Software Architect Should Know [Repost]
![97 Things Every Software Architect Should Know [Repost]](https://pixhost.icu/avaxhome/c0/17/002417c0.jpeg)
97 Things Every Software Architect Should Know by Richard Monson-Haefel
English | 15 Feb. 2009 | ISBN: 059652269X | 222 Pages | PDF | 1 MB
English | 15 Feb. 2009 | ISBN: 059652269X | 222 Pages | PDF | 1 MB
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology.
More than four dozen architects – including Neal Ford, Michael Nygard, and Bill de hOra – offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:
Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar)
Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm)
Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards)
Simplicity Before Generality, Use Before Reuse (Kevlin Henney)
For the End User, the Interface Is the System (Vinayak Hegde)
It's Never Too Early to Think About Performance (Rebecca Parsons)