10 Things Every Software Architect Should Know
Source: O'Reilly Media
This is really fantastic book; every software architect has to read. This is actually ninety seven Things Every Software Architect Should Know. From this ninety seven the author gave us only ten from extracting more important things. 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 hoar - 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, one will find useful advice such as Don't Put Your Resume Ahead of the Requirements, Chances Are, Your Biggest Problem Isn't Technical, Communication Is King; Clarity and Leadership, Its Humble Servants, Simplicity Before Generality, Use Before Reuse, For the End User, the Interface Is the System, It's Never Too Early to Think About Performance (Rebecca Parsons) and etc. To be successful as a software architect, you need to master both business and technology. This book tells one what top software architects think is important and how they approach a project. If one wants to enhance their career they should see the webcast.