ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1949 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
12 More Essential Skills for Software Architects
Dave Hendrickson
Paul Floyd
Appeared in:

In this follow-on book to 12 Essential Skills for Software Architects, we get coverage of the technical skills that mirror the soft skills. There is some overlap with the first book, and some of the chapters here seemed fairly ‘soft’ to me: partnership, governance, roadmapping and entrepreneurial execution. It wasn’t particularly clear to me how ‘software architecture’ differs from general software management and development, not that the title matters much.

For a book covering technical skills, I did expect some more concrete examples, perhaps some real world case studies would have helped. As it was, I was left wondering whether I was just reading sensible sounding platitudes, or whether there were any success/disaster stories when the advice was followed/ignored.

One chapter seemed a little odd to me, chapter 6 on ‘Platforms’. This more or less assumes that you work on a big system that will evolve to become platforms. Perhaps I haven’t worked on enough (or indeed any) many major governmental IT projects, but my experience is that after a couple of decades, code tends to evolve into multi-million line monoliths.

As with the previous book, the diagrams look a bit cheesy and don’t add much. For instance, is there really any reason why ‘Relevance’, ‘Excellence’ and ‘Currency’ should form a triangle?