This is a nice read for someone entering the software architecture domain. However, I would not recommend it as a reference book for a software architect without serious development experience for the following reasons:

- it tends to be a little to abstract (for a 700+ pages book I would expect to have at least an example for every concept)
- the "further reading" sections seem to be presenting the sources of the chapter (instead of giving useful/actual references to articles that would expand on the presented subjects)
- there's a compatibility matrix in the connectors chapter and it doesn't make any sense just by reading the text rendering it unusable
- some chapters are unconvincing (chapters about implementation or about security come to mind)
- sometimes it goes into detail to the code level and sometimes it stays at a very abstract (unpractical) level when making a point
- most of the times the recommendations/suggestions/guidelines are common sense (which is good in my opinion), but they are explained in too much detail which makes the reading boring.
- and another one... the assumption of the book is that you use sw architecture for big applications. And the examples are based on Lunar Lander? I doubt that one can explain every strength/weakness of architectural styles based on just that.
- and by the way... is the C2 style even used in practice???