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.

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 17 Ratings

Not worth the money - 2009-08-06
Reviewer Rating:
This book is just an accumulation random advice collected for "free" off a blog. You will feel like you have read a bunch of fotune cookies (i.e. "The longest trip begins with a single step") on the topic of architecture. Not a single topic is explored in depth since each topic is only 2 pages in length.

I would not recommend this book.

I want my money back - 2009-07-21
Reviewer Rating:
Heavy on keywords and low on actual content / value.

Imagine your Dad rings you up and says, "Be sure to go to work bright and early..." or "The early bird gets the worm" and proceeds to ramble on for 5 minutes about why that is important. We have all been through this kind of lecture. For politeness sake, you bite your tongue and zone out.

Now replace Dad with Bill Gates/ Steve Jobs/ some famous architect. However the advice being doled out is similar. eg. "Be sure to have a decent UI for every component/ blah blah blah".
How would you feel if you had to read 97 articles by famous architects / tech gurus, each 2 pages long and the entire content of the article is in the first introductory line itself. The rest is fluff.
I don't know about you, but when I am paying 20+ dollars for a book, I expect more than simple fluff.

-V

a collection of experience and wisdom - 2009-11-12
Reviewer Rating:
this book talks about different experiences of people, what they did wrong and what we can learm from them. this book did teach me a lot and would recomend this to be a must read.

Real world advice. - 2009-09-19
Reviewer Rating:
Real world architecture advice from real world architects. Some of the suggestions are really good. Gives you some insight into an architect's mind.

Not really about software architecture, but pleasant reading nonetheless - 2009-08-07
Reviewer Rating:
[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. Most people who consider themselves an architect, however, are probably merely applying the design and philosophy that somebody else created.

Setting aside the definition of architect, the advice is good for almost any project leader involved with software development no matter their job title. It's much better advice, however, for the journeyman who wants to be a project leader someday.

As with many management books, anecdotes are rife and facile. They are the sort of things you might mention in an elevator, such as changing the Mach 2.5 requirement of the then-future F-16 fighter plane to "escapes combat quickly", but that anecdote doesn't really help anyone, or at least not in the same way as something holistic and fleshed-out like Skunk Works: A Personal Memoir of My Years of Lockheed. I would have appreciated footnotes or references to complete case-studies.

Given the short format of each contribution, this generality is probably unescapeable. That's mitigated somewhat by the accompanying website for the book where longer discussions might take place. There's no overarching concept or guidance since the contributors are advising in different dimensions, coming from different experiences, and using their own idea of what a software architect should do. Very few contributors talk in terms of the complete software life-cycle; much of the advice in the vein is about requirements research, and even then is mostly about proper mindset rather than useful techniques.

Browse Similar Topics

Top Level Categories:
Software Engineering

Sub-Categories:
Software Engineering > Architecture
Software Engineering > DevMan