I disagree. It has plenty of useful information, but you have to take it all with a grain of salt. I'd much rather work with someone who has read and tries to apply Clean Code than someone who writes a 1000 line function.
> I'd much rather work with someone who has read and tries to apply Clean Code than someone who writes a 1000 line function.
Surely you recognise this is totally a false dichotomy?
I’d rather work with well structured 1000 line function than dozen useless functions from Clean Code.
I know exactly what you mean. I'm so happy that he only wrote about Java. Hardly imaginable how many damage this book would cause if it's written about C++.
Some of his points are good, some are bad. I think Clean Code should be read, but not considered the Bible. It's a good work with some flaws.
Thank you very much! Really! Since some years I puzzle to find out why the most Java programmers write code that is as shitty as it is. With tons of methods that are just doing more ore less nothing and you need to jump through 42 classes to find out what the code is really doing. It's a mess of code overhead that leads to nothing than more code overhead.
Now I know, it's because the existance of this book and most Java programmers think thats the clean way to code. Unbelievebal.
I sincerely doubt most Java programmers have even read the book
Clean Code has 4 great chapters, quite a lot of outdated Java-ese, and some in between.