3 ms·
Replying to my own comment. I'm now through Chapter 4 (Comments) of Clean Code, it'll probably be a few more days before I resume reading it (catching up on wor
by Jtsummers 5y ago
Replying to my own comment. I'm now through Chapter 4 (Comments) of Clean Code, it'll probably be a few more days before I resume reading it (catching up on work after being on vacation, both work work and yard work thanks to the damned dandelions that have sprouted in the week I was gone). At least through this chapter, I'm not seeing any reason not to recommend this book. Sure, after programming for nearly 30 years (self-taught as a kid, through college, and professionally now for over 15 years) there's not a lot new for me. However, nothing in these first four chapters read as bad advice or bad practices and actually matches pretty closely with guidance I've given people I mentor.
Perhaps this book had a greater impact on me when I read it than I believe. However, I already had a lot of habits and patterns in programming by then that I don't think changed a lot after I read it the first time in the early 2010s. Maybe the next thirteen chapters will change my opinion, but at present I'm still inclined to include it in a short list of books I'd suggest to mentees and really don't get the hate it was getting in the other discussion.
That said, I've always been a synthesist. I acquire information and ideas from wherever I can find them, and put them together to form my own concepts and techniques. I would not recommend this as the book on clean coding practices. But it is certainly a book on the topic and has useful material especially for someone with just a few years of experience post college.
- dave_sid 5y agoI agree. It’s seems to be fashionable to bash this book at the moment but I can’t see how you would call any of the content ‘bad advice’. It’s not that different to the advice given in dozens of others.