I am really confused by this book. The summary looked really interesting, but I think author failed to deliver on the initial "promise".
I am not sure why I did not enjoy this book much. I think it may be because it was aimed at more junior engineers, it could also be because I did not manage to grasp author's vision and the core message.
I found first quarter of the book attempting to explain simple definitions in a little bit strange or confusing ways. Then author described some of the things, that architects should consider in their daily work. Author spent some time discussing different ways of documenting, modelling and diagramming solutions. Finally, he went through some of his observations of agile/waterfall teams and software architecture as a technical leadership role.
Some of the ideas in the book were sound, but I found most of the material fairly vague and more like common sense, rather than well structured and well thought out information.
Final score 6/10
About the author
Hi, my name is Artur Ejsmont,
welcome to my blog. I am a passionate software engineer living in Sydney and working for Yahoo!
If you are into technology, you can order my book Web Scalability for Startup Engineers on Amazon. I would love to hear what are your thoughts so please feel free to drop me a line or leave a comment.