I have been a senior developer for a while and have been trying to become an architect (by doing some parts of the architect's role).
How is the book going to help me transform into a complete architect?
Are there real business examples/scenarios that a developer can relate to in the book?
Although I'm not the editor of 97 Things Every Software Architect Should Know, it has a similar structure and intent to the 97 Things Every Programmer Should Know book I edited. The book is not a book of case studies or worked examples and it does not have a structured narrative dictated by the editor. It comprises a set of individual and focused items from a range of contributors. What you are likely to learn is perspectives, good quotes, provocative questions and opportunities for further learning.
I hope that helps.
Seriously? That's what you're going with? I prefer this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!