97 Things Every Software Architect Should Know and over 2 million other books are available for Amazon Kindle . Learn more

Buy New

or
Sign in to turn on 1-Click ordering.
Buy Used
Used - Good See details
Price: 15.75

or
 
   
Trade in Yours
For a 3.37 Gift Card
Trade in
More Buying Choices
Have one to sell? Sell yours here
Sorry, this item is not available in
Image not available for
Colour:
Image not available

 
Start reading 97 Things Every Software Architect Should Know on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

97 Things Every Software Architect Should Know [Paperback]

Richard Monson-Haefel
3.3 out of 5 stars  See all reviews (9 customer reviews)
Price: 22.50 & FREE Delivery in the UK. Details
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 7 left in stock (more on the way).
Dispatched from and sold by Amazon. Gift-wrap available.
Want it tomorrow, 23 July? Choose Express delivery at checkout. Details

Formats

Amazon Price New from Used from
Kindle Edition 12.71  
Paperback 22.50  
Trade In this Item for up to 3.37
Trade in 97 Things Every Software Architect Should Know for an Amazon Gift Card of up to 3.37, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Book Description

15 Feb 2009 059652269X 978-0596522698 1

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.


Frequently Bought Together

97 Things Every Software Architect Should Know + 97 Things Every Programmer Should Know + 97 Things Every Project Manager Should Know
Price For All Three: 61.08

Buy the selected items together


Product details

  • Paperback: 222 pages
  • Publisher: O'Reilly Media; 1 edition (15 Feb 2009)
  • Language: English
  • ISBN-10: 059652269X
  • ISBN-13: 978-0596522698
  • Product Dimensions: 22.7 x 15.5 x 1.3 cm
  • Average Customer Review: 3.3 out of 5 stars  See all reviews (9 customer reviews)
  • Amazon Bestsellers Rank: 347,321 in Books (See Top 100 in Books)
  • See Complete Table of Contents

More About the Author

Discover books, learn about writers, and more.

Product Description

Book Description

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)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:


Customer Reviews

Most Helpful Customer Reviews
22 of 22 people found the following review helpful
1.0 out of 5 stars More fluff than substance 17 Feb 2010
Format:Paperback
This is *not* a book by Richard Monson-Haefel but rather a collection of short and content-light pieces by a number of different writers you've probably never heard of. Indeed the pieces would be too short to even qualify as a magazine article.

Each 'chapter' is typically three, short, paragraphs of bland generalisation. Introducing each 'chapter' is a piece of fluff about the writer (think mini-CV crossed with an advert) which is often a significant fraction of the 'chapter'. And where the same writer has authored more than one chapter the fluff about him is repeated.

A very, very high noise to signal ratio and what signal there is is of very low quality.

Avoid.
Comment | 
Was this review helpful to you?
3 of 3 people found the following review helpful
3.0 out of 5 stars Good read during boot up 1 Oct 2009
By CT
Format:Paperback
The articles in the book are very short. I read three or four when booting up my machine on the morning.
These aren't the type of article that will give you a detailed insight into a topic, example: stand up when talking in a meeting. However, they are good tips for performing better in your job.
Comment | 
Was this review helpful to you?
7 of 8 people found the following review helpful
5.0 out of 5 stars I like it 26 Mar 2009
Format:Paperback
97 Things Every Software Architect Should Know is a book about things which are obvious and every software architect should know, remember and employ. The problem is that most things you can find inside the book are easily forgotten, underestimated and usually not implemented during day-to-day work.

The book consists of 97 short essays. Each of them deals with a vital problem software architects often have to face. Although there are great number of brilliant stories in the book I especially like the one titled: You're Negotiating More Often Than You Think, which is about a project sponsor wanting to cut down expenses. Does it sound familiar to you? Do you know what to do when it happens? The book is a collective work which makes it even more valuable.

Every day in the morning I start my work reading 1-3 essays to keep good practices in my memory and not forget management pitfalls lying in wait for me round the corner. I believe it helps me to become a better software architect. This book is a great and rare opportunity to learn from real experts in the field.
Comment | 
Was this review helpful to you?
1 of 1 people found the following review helpful
5.0 out of 5 stars Good checklist for any software architect 8 May 2012
Format:Paperback|Verified Purchase
You can't judge a book by its cover but you can certainly ask questions about its title. Why '97 things every Software Architect should know'? Why not 98, 99 or even 100? Well the word on infoq ([....]) is that they wanted a number near 100 so that there would be enough material for a reasonably sized book. Fair enough so... The book contains 97 articles published by a range of software professional expressing their views on various aspects of software architecture. Many of the articles are not very technical in nature and there are - perhaps - a lot of similarities between this book and '12 Essential Skills for Software Architects' where author Dave Hendricksen focusses on non-technical skills essential to be a succseful architect. Other articles probably aren't just things an Architect should know but really things anyone working in Software Engineering could benefit from knowing and thinking about. I even include Project Managers in that!

That said, there are some really enjoyable bits and pieces. My favourite parts:
* Keith Braithwaite's reminding of the architect's need to quantify things. Characteristics such as average response
time should be not be phrased using terms such as 'good' or 'satifactory' but quantified as something like:
'between 750ms and 1,250ms'

* Craig Russell's points about including the human interaction time in any performance analysis. The system
may respond very fast to API calls, but the if the UI is counter-intuitive, it means the user will spend a longer time try to
get his result.

* Michael Nygard advice for engineering the 'white spaces'. Don't just have arrows between components specifying the
communication protocol, describe the performance expectation of interaction e.g.
Read more ›
Comment | 
Was this review helpful to you?
4.0 out of 5 stars Excellent, easy to read short snippets 24 Mar 2011
By Ollie C
Format:Paperback|Verified Purchase
Books like this one are great for those with little time - featuring short learnings / tips on a topic- as they are easy to pick up and put down - unlike books that have heavy long chapters.

A great way to learn from seasoned experts in the field. Covers a wide range of topics from patterns to team communication. One of the best IT Architecture books I have read in a while.
Comment | 
Was this review helpful to you?
Would you like to see more reviews about this item?
Were these reviews helpful?   Let us know

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 

Search Customer Discussions
Search all Amazon discussions
   


Look for similar items by category


Feedback