- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
97 Things Every Software Architect Should Know: Collective Wisdom from the Experts Paperback – Feb 15 2009
|New from||Used from|
Special Offers and Product Promotions
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
Collective Wisdom from the Experts
About the Author
Richard Monson-Haefel , an independent software developer, coauthored all five editions of Enterprise JavaBeans and Java Message Service (all O'Reilly). He's a software architect specializing in multi-touch interfaces and a leading expert on enterprise computing. More detail on his work and writings can be found at www.monson-haefel.com.
Inside This Book(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
Interesting reading if you are already in the architect role and want a reminder of those things you should be doing, but you'll need to know the details behind the advice to really make use of it. Worthwhile if that's what you're looking for.
The format of the book is such that each entry takes up 2 pages. However, most entries only need close to 1 page, so much of the book is white space. On the plus side, it's very small and light to take with you on the bus.
If you like reading blog entries that are mostly opinion pieces about the topics around software architecture (including personal communication, teamwork, business challenges, etc.), this might be a really good fit for you. I found that too much of the content is simply common sense.
Of course, our industry isn't the best at always applying common sense, so perhaps some people might find this useful as a gift to their coworkers. I would choose to apply my personal time and money elsewhere.
This makes it not only easy to read,but one can literally jump to any part of the book.
The context offered is from architects with real experience.
Most Helpful Customer Reviews on Amazon.com (beta)
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.
I would not recommend this book.
such a useless, incoherent and impractical amount of pseudo-advice?
His other books provided deep technical knowledge and practical help.
This one's not worth its price - there are much better books available...
alternatives: Taylor et al: Software Architecture (Foundations, Theory and Practice): Great read.
Bass et. al: Software Architecture in Practice: Great read.
Buschmann et. al: Pattern-oriented Software Architecture: Great series.
Fowler: Patterns of Enterprise Application Architecture: Great, highly practical...
So - don't bother with this one, go get a good book :-)
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.
Look for similar items by category
- Books > Computers & Technology > Computer Science
- Books > Computers & Technology > Hardware > Design & Architecture
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Professional & Technical > Engineering > Civil
- Books > Textbooks > Computer Science & Information Systems > Programming Languages
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering