I think the problem with this book is not about recipes it gives, and way how it approaches the problem, but the problem itself. I spent 8 years working in diff

I think the problem with this book is not about recipes it gives, and way how it approaches the problem, but the problem itself. I spent 8 years working in different software companies, and never met a person with the 'architect' job title, whose job would be different from one of either developer or manager. Therefore, I personally do not believe in 'software architects'. And this book supports me in this! I went carefully through the list, diving inside some specific topics and it seems that all of them (or overwhelming majority) lie in the field of responsibility of someone who could be described by job title other than architect. "#12 There is no one-size-fits-all solution" -- fine, development issue. "#17 Business Drives" -- fine, management issue. And the the brightest gem of all: "#80 Dont Be a Problem Solver".