Has anyone read Uncle Bob's last book Clean code?
UPDATE:
Is it similar to Martin Fowler's "Refactoring"?
+15
A:
Clean Code is a wonderful manual that encourage you to think deep and hard about all the small things, all the little details that makes your code base not only a place to work but a thing of beauty and a comfortable environment for you and your team to be creative.
In short, it's a wonderful book and I highly recommend it.
Torbjörn Gyllebring
2008-09-26 20:09:23
Did you read Refactoring? is this book like it?
Pablo Fernandez
2008-09-26 20:10:12
Refactoring is a great book with many nice recipies and structural things to think about, Clean Code goes on another level talking about the need to have common conventions, dissecting how to write functions in a good way, how to deal with tests and concurrency. Basicly all the "must do"'s needed.
Torbjörn Gyllebring
2008-09-26 20:14:50
Yup, its really inspiring. Still not read more than the first few chapters, but it is compulsive reading.
Bjørn
2009-08-23 18:27:08
+1
A:
If I had not read Kent Beck's excellent "Implementation Patterns" book, I might have been more impressed by "Clean Code". I prefer "Implementation Patterns" because it is more concise, and was easier for me to internalize.
Pokus
2008-09-26 20:09:32
+1
A:
For a book like refactoring I would say that Refactoring to patterns is a great resource. Clean Code is more about basic hygine factors like how to structure your source code, the value in having clear intent revaling names, the necissity of testing etc. I put it in the same category (albit it's the most code centric in the bunch) as The Pragmatic Programmer and The Productive Programmer.
Torbjörn Gyllebring
2008-09-26 20:19:53
+1
A:
I would recommend this book aswell. I would actually place it (topic wise) more or less together with "Code Complete 2". Both books talk about how you can improve your code quality.
Clean code is java focused, but still readable for C# programmers. Although some conventions are java only. He also talks about how he hates I infront of every interface (ICollection or whatever), and how he thinks functions should be named.
The book is also nice in the way it looks at other famous programmers and incorporates some of their thoughts into the book. I really like the book, infact I'm re-reading it, to make sure I will remember every line of it :)
Tomh
2009-02-11 22:02:34