Scan barcode
jonathonjones's review against another edition
3.0
If this is the first book you read on this topic, you will probably like it better than my 3 stars. And if you program in Java, you will also like it better. Personally, I mostly work in Ruby and have read a lot of material that was similar to this (probably based on this!). So my unfair, subjective rating is that this didn't add a lot to what I already knew, but is a perfectly reasonable version of this type of book.
duesenklipper's review against another edition
3.0
Many good points in this book. Unfortunately, almost all of them are overdone. Yes, you should write short functions, if possible. Yes, you should have functions that do one thing.
But no, "one thing" does not mean you should tear an algorithm apart into twenty little funclets that make no sense on their own.
Basically, like another reviewer wrote, the first part of the book raises many good points, and the second part of the book then merrily applies these points way beyond their usefulness. Read the book, but keep your brains turned on and be alert.
But no, "one thing" does not mean you should tear an algorithm apart into twenty little funclets that make no sense on their own.
Basically, like another reviewer wrote, the first part of the book raises many good points, and the second part of the book then merrily applies these points way beyond their usefulness. Read the book, but keep your brains turned on and be alert.
nikolastoti's review against another edition
4.0
Work-related read: The first half of this book is pretty excellent. The latter half is a bit too language specific for me to be able to follow along (even tho the concepts arent). Overall definitely made me a better coder and I think most people should read the first half during their first year of coding.
brunjact's review against another edition
3.0
This book has a loot of good advise which I try to make use as much as possible. I take away three main features from this book: 1) the author presents and demonstrates the practice of clean coding habits; 2) the author lists his own set of heuristics and code smells; 3) the author demonstrate in a refactoring session how he identifies code smells and applies heuristics to clean up code.
My let down of this book is that is — at times — very Java intensive. Had I known this beforehand I might have picked up another book instead. I skimmed some of those sections since they don't relate to my the one I'm using now — Ruby.
This book will gladly sit on my shelf with a bookmark on the Smells and Heuristics chapter.
My let down of this book is that is — at times — very Java intensive. Had I known this beforehand I might have picked up another book instead. I skimmed some of those sections since they don't relate to my the one I'm using now — Ruby.
This book will gladly sit on my shelf with a bookmark on the Smells and Heuristics chapter.
omarelkhatib's review against another edition
4.0
Read it with open mind,
I didn't agree with everything Author said,
But overall good lessons there.
I didn't agree with everything Author said,
But overall good lessons there.
maxpatiiuk's review against another edition
3.0
FYI: I read a modified version of this book adapted for JavaScript - https://github.com/ryanmcdermott/clean-code-javascript
The material is quite OOP-focused - a lot of the things don't apply in functional programming or have to be adapted. Not surprising, since it was written with Java in mind.
Still, there are some good principles in here - though not much new for me.
The material is quite OOP-focused - a lot of the things don't apply in functional programming or have to be adapted. Not surprising, since it was written with Java in mind.
Still, there are some good principles in here - though not much new for me.