Top critical review
Mostly good lessons but not a good format
Reviewed in the United States on May 7, 2019
It feels like a collection of 30-60 minute slideshow talks pasted together into a book. There are a lot of bullet points and a lot of those could be removed without hurting communication. I think one's time would be better served by reading something like The Architecture of Open Source Applications, and authors like Joel Spolsky.
For such a new book there's already quite a bit of link rot. The related online forum is also shut down, presumably just out of protest, since I doubt the FOSTA concerns were really relevant.
I did like a good chunk of the content. I liked the grounding of architecture as being about expressing quality attributes. I liked the bits about actually quantifying risks instead of letting stand vague objections like "this is risky". I liked the suggestions to improve diagrams (and types of diagrams) and to create things like empathy-maps to better understand user scenarios. I liked that the book has color! As a reference, the third section of the book can be useful for certain circumstances.
Unfortunately few circumstances apply in my BigCo role, but that's more the fault of the BigCo, I didn't expect this book to cover anything about moving from some other way of designing software to the way described in the book. (One might be amused to know that this was read in an office book club setting at same BigCo.) I would be interested in reading about how the author integrated or was unable to integrate things from this book in is work at IBM, another BigCo. I thought the example case-study wasn't that useful, but further would have appreciated it as its own standalone chapter near the end instead of handed out drip-by-drip at the end of each chapter, or some real case studies.