It may not be possible for us to ever reach empirical definitions of "good code" or "clean code", which means that any one person's opinion about another person's opinions about "clean code" are necessarily highly subjective. I cannot review Robert C. Martin's 2008 book Clean Cod...
When I read clean code (about 2 years ago), I read it with the point of view of a C++ programmer. I read the advices and skept the code (since java didn’t interest me that much) and I filtered the advices that I though didn’t applied to C++. For this very reason, I found the book relatively good (since I focused only on the good part).
I found this article absolutely on point. I also finally understand why I really don’t like uncle bob’s conferences since I don’t skim or filter them partially but watch the whole content.
Nonetheless, I don’t regret that I read clean code, mostly because it forced me to articulate my thoughts on what I liked/disliked about it. I wouldn’t recommend it though.