Reviews
Great book for everyone who wants to be a professional programmer. This book consists of many chapters that mainly talk about how to write code cleanly such as naming convention, function, class, comments,... All of these things made me wow many times with the explicit examples. But the Java language used to illustrate the code might confuse me a bit (cause I’m kinda bad at Java lol). I skipped a couple of pages about Java’s lib and concurrency programming. Anyway I would highly recommend this book for everyone especially new programmers like me for a better orientation. :D
I loved the philosophy and spirit beyond the writing! Yet for some reason I do believe it was odd and old fashioned for some topics! Yet It is a good knowledge and good do pass by! Merged review: I loved the philosophy and spirit beyond the writing! Yet for some reason I do believe it was odd and old fashioned for some topics! Yet It is a good knowledge and good do pass by
I loved and I agree with the clean code values the book embodies. Also, I loved the slight extremism of the rules: never write a function more than 15 lines, never use more than 3 arguments! Of course I will break those rules. But remembering Uncle Bob's fervor when stating the rules, I will always make sure to have a good reason to break them. The major drawback is that the book is very Java-centric and the examples didn't prove as practical for me, as they could've been. Abstract classes, interfaces, class hierarchies, verbosity. Yet, without the examples, all the values, rules, and heuristics would've been lonely and hard to pay attention to. I am sure everybody will find something to love about Clean Code.
Highlights
It is not the language that makes programs appear simple. It is the programmer thatmake the language appear simple!
wrt Ward Cunningham's contribution
Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.
Grady Booch, author of Object Oriented Analysis and Design with Applications
I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and performance close to optimal so as not to tempt people to make the code messy with unprincipled optimizations. Clean code does one thing well.
Bjarne Stroustrup
We’ve all looked at the mess we’ve just made and then have chosen to leave it for another day. We’ve all felt the relief of seeing our messy program work and deciding that a working mess is better than nothing. We’ve all said we’d go back and clean it up later. Of course, in those days we didn’t know LeBlanc’s law: Later equals never.
Martin is saying if the code you commit isn't clean, it never will be. So … never write anything but clean code?
specifying requirements in such detail that a machine can execute them is programming.
Martin's definition of programming.
This book appears on the shelf 2016-reads
This book appears on the shelf Shorties read
This book appears on the shelf Childhood books
