Goodreads helps you keep track of books you want to read.
Start by marking “97 Things Every Software Architect Should Know: Collective Wisdom from the Experts” as Want to Read:
97 Things Every Software Architect Should Know: Collective Wisdom from the Experts
Enlarge cover
Rate this book
Clear rating
Open Preview

97 Things Every Software Architect Should Know: Collective Wisdom from the Experts

3.55 of 5 stars 3.55  ·  rating details  ·  330 ratings  ·  29 reviews
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 less ...more
Paperback, 222 pages
Published February 12th 2009 by O'Reilly Media (first published January 1st 2009)
more details... edit details

Friend Reviews

To see what your friends thought of this book, please sign up.

Reader Q&A

To ask other readers questions about 97 Things Every Software Architect Should Know, please sign up.

Be the first to ask a question about 97 Things Every Software Architect Should Know

This book is not yet featured on Listopia. Add this book to your favorite list »

Community Reviews

(showing 1-30 of 963)
filter  |  sort: default (?)  |  rating details
سامح السيد
If you are familiar with Agile software development and Domain Driven Design, you will find many of the tips in the book have relevance!
To sum up the most important things I got from the book:
- Go Agile, Go Agile, Go Agile
- Design patterns is important (they are not those of GoF patterns only), but you should know anti-patterns, and refactor to patterns not try to force applying them in the first place!
- An architect is a leader as well
- An architect should have hands on experience, and can writ
A collection of 97 two-page essays by 97 software architects about things they think every software architect should know. Most of them are very reasonable (don't use clever tricks; don't let your software have too many layers; understand that the usual abstractions are broken in the error cases). Some, however, are strange (be a good manager for different kinds of people as described in Neal Stephenson's Cryptonomicon; realize that software architecture has ethical consequences? it does, but th ...more
97 two-page pieces of advice about software architecture. Since each entry is only two pages, there's a limit to how in-depth they can be, so they tend to stay fairly general.

There's a few good points here and there, but I think I've already forgotten most of them again.
Alex Ott
Main problem with this book, is that isn't real book - it set of very short essays, that almost not linked to each other excluding mega-topic called "software architecture".
So it very inconsistent - after essay on performance, goes essay on communication skills, then essay on code organization, etc. It's hard to read such things...
It's better to read normal books, like "Release It!", "12 essential skills for software architects", etc. if you want to read something about software architecture pro
Robson Castilho
This book is a set of 97 short essays written by a lot of software architects. It brings us nice advises encompassing technical aspects and soft skills.
Easy and fast reading, it's a good book for everyone who wishes to understand better the skills needed to a software architect and a good start to think about the "big picture" of a software project.
Kuoting Cliff
For someone without a background in software engineering, but am in great need of some of their lingo, the book provides some nuggets of takeaways! Nonetheless, although the book looks thin, it took me quite some time to get through it. Most probably due to all the notes that I had to take from reading the book.
Burak Yigit Kaya
First of all this is not a book in the traditional sense. It is a fine collection of various short to mid-length articles from various architects.

Some of the points and advice given in the book may sound like common sense but putting them on paper and expanding some of those ideas makes a real difference. This book might have the most bookmarks and highlights in a book on my Kindle which I think is a great thing.
Jan 21, 2015 Luiz rated it 4 of 5 stars
Shelves: 2011
Coleção de micro-artigos de uma página. Dá para ler online.
Wynand Pieters

First off, this "book" is getting some bad scores because of the format. Ignore that, and see it for what it is. It's a collection of thoughts and advice from experienced architects and industry leaders. Many points should be familiar to any skilled or experienced software architect. Many of these are "common sense" ideas, but as we quickly learn in the real world, common sense isn't. It is good to be reminded of these points mentioned in the collection, as many architects lose sight of them ov
Olli Sorje
Has thoughts from different kind of perspectives. Mostly nothing special, but gave me some new ideas how to view things.
low on actual content but some suggestion is valuable
Said A
Short and easy read. 97 tips and thoughts of software architects mostly unrelated to one another but almost all of them come down to some basic rules (like: clear communication, healthy environment, follow tested best practices of software development, know what you are doing, etc.).

I gave 4 stars because you can take any of 97 "things" from the book, read it and reflect on your own experience. Thus reminding yourself the lessons you learnt from you previous projects/failures. So this book is as
Miguel Duarte
I wouldn't call this a "book". It's more like a compilation of short tips on how to be a good software architect. While some of the advice is genuinely good, the book's fragmentation makes it very boring to read. There is no connection between the 97 (!) parts, which made me put it down many, many times. In fact, it took me over an year to finish this 200 page book! The content is available online for free on O'Reilly's website, so just take a look there. Having this many "blog posts" compiled i ...more
Franck Chauvel
This book contains 97 essays by experienced software architects. Each one describes specific aspects of software architecture: nature, realization, how to behave, how to interact, etc. To my opinion, key messages includes keep the architecture simple, understand the business side, keep in touch with technical side, be flexible and agile. Yet, one may regret the lack of structure of the book as nothing relates all these short essays.
Perfect to read just a few pages at a time, this book distills many essential insights on architecture. There is no structure in the book, it is just a collection of very small articles from many authors. Not all articles are equally interesting, however it's a pleasant read and it is really useful for anyone involved in software architecture.
Sergey Zubov
Эта книга будет интересна не только архитекторам ПО, но и всем, кто вовлечен в процесс проектирования ПО. Часто авторы предстают Капитанами Очевидность, но есть и довольно неожиданные советы. Если собираетесь читать в русском переводе, то он вас не разочарует, переводчики потрудились на славу.
Dave Bolton
This is a collection of mostly obvious but occasionally insightful essays about software architecture. Really, the main takeaway is that architecture is about reducing friction, surprise and complexity, which means this collection is actually largely ho-hum to read.
Mas bien son como unas veinte cosas que hay que saber repetidas 97 veces. Aceptable, no introduce ningún concepto técnico imposible de comprender, de fácil lectura. Cada capítulo lo deja a uno con la sensación de "Eso ya lo sabía".
97 tips related to software architecture, provided by some of the most respectable people in the industry. Nothing new or shocking, but it is a good read for a couple of evenings' worth of spare time.
Mostly all of those 97 tips came from common sense. Even everything written in this "book" is actually a obvious must-know I liked it, it brings all the things together in one place.
Mitul Golakiya
Some of the topics are really helpful...
Every architecture should give it a time...
Sergio Venicius
Nice book about facts that we software engineers deal everyday. Good to think about.
if you call yourself software architect, this book is full of real life advices
Great. Though only for those who have experience on enterprise level project.
Julian Haeger
Nice nuggets which are easy to read in a couple of minutes.
Features an article from Kamal Wickramanayake
Corey Kimball
Word; lacks substance; had a few key-points.
gr8 recommend for every programmer...
« previous 1 3 4 5 6 7 8 9 32 33 next »
There are no discussion topics on this book yet. Be the first to start one »
  • 97 Things Every Programmer Should Know: Collective Wisdom from the Experts
  • Beautiful Architecture
  • The Productive Programmer
  • Refactoring to Patterns
  • Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers)
  • Xunit Test Patterns: Refactoring Test Code
  • Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
  • Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
  • Beautiful Code: Leading Programmers Explain How They Think
  • Lean Software Development: An Agile Toolkit for Software Development Managers
  • Masterminds of Programming: Conversations with the Creators of Major Programming Languages
  • Software Estimation: Demystifying the Black Art
  • Growing Object-Oriented Software, Guided by Tests
  • Ship It!
  • Patterns of Enterprise Application Architecture
  • Agile Software Development, Principles, Patterns, and Practices
  • Continuous Integration: Improving Software Quality and Reducing Risk
  • Facts and Fallacies of Software Engineering

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »
Enterprise JavaBeans 3.0 J2ee Web Services Enterprise JavaBeans (Java Series (O'Reilly & Associates).) Enterprise JavaBeans Learning the iPad SDK

Share This Book