I just learned about the existence of this book a few minutes before seeing this post (what's the name of the phenomena whereby after discovering something once, you immediately observe it again?), and the M.O. of the book resonates with me; I do lots of refactoring, as well as a fair amount of API design, and I've always put a lot of thought into the "best" way to write code. E.g. while I personally enjoy writing clever code, such code is usually a detriment in a team environment. I also get irritated when others don't put time & effort into writing clean code (or at least putting a minimal amount of thought and effort into it).
But I see that there's some pushback against this book, and so I'm not sure if it's all that it's cracked up to be. Anyone have any opinions?
Yes, that's it! Oddly enough, I can never remember the name of it. I'm going to attempt to commit it to long-term memory by classifying it as a cognitive bias; hope it sticks this time...
I, for one, recommend "Clean Code". It did not "change my life" because I was already on the path the book describes. Nonetheless it was a good validation, it certainly coalesced in a good form many topics that were simply fluctuating in my mind, and is a good reference to have around for refreshing once in a while.
To put this in context: I keep it next to "Agile Software Development" (by the same Uncle Bob), "Working Effectively with Legacy Code" (by M. Feathers), and "Refactoring" (by M. Fowler).
HTH (no, I have no direct or indirect benefit from 'advertising' these books and their authors)
But I see that there's some pushback against this book, and so I'm not sure if it's all that it's cracked up to be. Anyone have any opinions?