Rating:
(29 reviews)
Author: Richard Monson-Haefel
ISBN : 059652269X
New from $17.36
Format: PDF
Direct download links available 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts Free Download for everyone book 4shared, mediafire, hotfile, and mirror link
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) To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.
Direct download links available for 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts [Paperback] Free Download
- Paperback: 222 pages
- Publisher: O'Reilly Media; 1 edition (February 12, 2009)
- Language: English
- ISBN-10: 059652269X
- ISBN-13: 978-0596522698
- Product Dimensions: 0.5 x 6 x 9.2 inches
- Shipping Weight: 8.8 ounces (View shipping rates and policies)
97 Things Every Software Architect Should Know: Collective Wisdom from the Experts Free Download
[97 Things Every Software Architect Should Know] is much more broad than most people would expect from its title. It's certainly true to its title, but I expected that it would have be 97 things software architects should know about software architecture. Many of the points, while good advice otherwise, aren't special to software or software architecture. They are points any manager, project leader, or executive could apply. It's really 97 Things Every Project Manager Should Know, although there's already a book for that.
The first thing every software architect should know is what is expected from that job title, and I was hoping someone would at least try to define it. In reality, the title is a dumping ground for the tasks you don't give to the programmers but don't trust to the executives, and the job description varies widely.
My notion that nobody really knows what a software architect should do is reinforced by reading the advice from the many contributing experts, each of which briefly write about what they think is important. Some of that advice conflicts with other contributors, is so general so that the it would suitable in any business book, or merely shows that anyone touching a keyboard might be labelled a "software architect".
I was surprised that a lot of the advice tried to actually force the commoditization of "software architect", as if the actual person doing the job was interchangeable. An architect's experience, vision, and artistry should be at the center of the endevour. Architects are not cogs; they create and enforce the philosophy and design concept. In that regard, I actually only know a handful of software architects.