posted 11 years ago
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.