3 ms·
Does anyone have any opinions on "Uncle Bob's" Clean Code [0] book? I read bits and pieces of it but never sat down and gave it a thorough read. [0] https://ww
by Jerry2 8y ago
Does anyone have any opinions on "Uncle Bob's" Clean Code [0] book? I read bits and pieces of it but never sat down and gave it a thorough read.
[0] https://www.oreilly.com/library/view/clean-code/9780136083238/ https://www.oreilly.com/library/view/clean-code/978013608323...
- raiflip 8y agoIt's pretty good. Depends on your skill level. It focuses on how to write algorithm, classes, and grouping classes into modules in a way that is considered "clean". He has another book on clean architecture that deals with structuring programs.
- yesenadam 8y agoClean Code (2008) is at the top of my Books I wish I'd read 10 or 20 years earlier list, along with Refactoring (1999). They totally transformed the quality of my finished programs, in many ways. Some what I learnt may fit into "That's so obvious, why didn't I think of that", or making conscious the things you already do... Refactoring, just by naming and defining the activity, was useful. They're both talking about the programming equivalent of editing for writers. And how to do that, how to get from the 'dirty code' first draft to the 50th draft with everything as good as it can get. Do your future self (and other people) a favour - they're the ones who will have to read and understand your programs. A couple of years later I came across Allen Holub's Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming (1995). I didn't learn anything from it, but it contains almost all of what's in those 2 books, and was written years earlier, (so could have been read earlier), and I think he deserves more credit.