Not really. Or in regard to parallelism and some other specific and mainly related to Java points.
I read this book in two or three days (I'm pretty passionate about it). Here's what I think:
- Most - if not all boards are legitimate. However, they are mostly already widely discussed in Code Complete and Craft Code.
- The author seems so sure of himself that he rarely gives references. Although Code Complete is based largely on serious studies, Clean Code is first and foremost based on the aesthetics of its author. When the first said, "You should do this because studies have shown that ...", the second says "Do this. And that is why I think it's better ...". The impression left by the tone is rather unpleasant.
- Developers who do not use Java will remain somewhat unsatisfied. Although Code Complete attempts to be agnostic in terms of language, Clean Code resolutely Java. That said, we can easily adapt to C # and VB.NET.
- Agile Development: the word is fashionable, we use everywhere to sell some more. Clean code is not agile than are Code Complete and Craft Code. I even thought he was a little less, but it is an impression.
I put 4 stars because too few computer scientists read that kind of book, however, essential. If you have any books on the subject, read Code Complete. Then either, Craft Code Clean Code or (my preference from the first - the author does not give the idea of innate knowledge).
That said, if you do not have access to the first two, Clean Code is a very good book.
