david.doolin

Read this as part of a Bradfield course. Packed with ideas, some more useful than others at any given time, but definitely worth reading.

Read this 10 years ago. It was profoundly influential then. Due for a reread.

Read this as course material for a Bradfield leadership class.

Nice survey of thinking current to publication date. While the leading edge has moved on, the book provides an easy entry into service construction, and in many cases, that may be all that's needed.

I worked through the book implementing the code as I read. Definitely worthwhile. Probably worth a reread/rework.

I really liked this. I had it first as a textbook, then read it cover to cover several years later. Sadly, I cannot find my copy at the moment.

Very good insight, not a silver bullet.

Read this several years ago, need to reread it.

I liked Phoenix Project a bit better.

My rating of 3 reflects my point of view coming from the engineering side. That is, I did not feel this book was overly helpful when I was working mostly as an individual contributor. I might well find a reread more useful being more on the management side.

Read this years and years ago, it's on my list to reread.

The software industry would benefit using methods advocated by this book.

Read this a few years ago. Some really interesting ideas, not sure how well-supported the science is.

Read this as part of Bradfield Leadership course. Worth a reread.

This was a NYT bestseller for a reason: it's an excellent account of how a short sequence of intense, bloody battles convinced both sides that they had won the battle, and had the keys to ultimate victory. In 1965.

First read this in the 1980's. Lot of lessons here, even for software development.

I've read this completely through at least twice, and taken notes on several chapters. Worthy reference.