Unlike in "Clean Code" Robert Martin goes in "The Clean Coder" not on the result of the programming work - the code - a, but is dedicated to the extensive process of programming and the professional behavior of software developers in the business environment. Anyone who seeks advice for programming or to further optimize its code, will definitely be disappointed. However, those who are looking for solutions or recommendations for frequent problems in interpersonal relationships of software development ("soft skills") is, the was "The Clean Coder" highly recommended. While Martin goes in separate chapters also (superficially) on more technical issues such as TDD, code katas and test strategies and lists annexed a few more important that he uses tools for programming, but the majority of the book deals with the effective communication with colleagues ( esp. managers) and the "programmer honor".
Robert Martin mediates its "lessons learned" in particular with practical examples from his own career. This partly decades past opinions are very entertaining and show that the field of software development has yet changed less over the many years, as one might assume. Much is still as valid as it was then, about the frequent misunderstandings between managers and developers in estimating project duration, or the belief that one can keep the deadline somehow with some overtime. Martin makes on the basis of the errors made by him for a professional behavior as developers strongly, for example, for saying no to impossible demands or responsibility, constantly renew and therefore closes the book with his definition of "Software Craftsmanship" from whose advocates he is.
Ultimately many claims in "The Clean Coder" were already known to me from other books or could be placed with a little common sense itself, but no one will take you as good and absolutely entertaining to the point as Robert Martin. As one might summarize the key messages of the book in a few pages and Martin in some places partly repeated complete anecdotes to emphasize his statements again, there is of me in the assessment a deduction of points. But through my mind well-written stories and the relatively small size of the book it is slightly overall and liquid read in a few hours and therefore highly recommended each entry in the topic "Software Craftsmanship".