Product Details
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
6 of 6 people found the following review helpful:
4.0 out of 5 stars
Be a professional,
By
This review is from: Clean Code: A Handbook of Agile Software Craftsmanship (Paperback)
If you want to be inspired to be a true professional programmer, Clean Code is a great book. A variety of topics are covered including naming, comments, formatting, exception handling, testing, and concurrency. Once you've read the book, the reference chapter on smells and heuristics is probably what you'll return to the most.
The common theme that runs through the book is the push to be a true professional when programming. More often than not we get something working and then move on, saying that we'll write the tests or refactor it later. A professional will clean up the mess immediately before moving on to the next task. In this sense the book is inspiring if these goals are in line with yours. In some ways the book reminds me of Code Complete, but if you already have read that you will still find new content, in particular with the exhaustive examples that show various clean ups including a portion of JUnit. A couple of the examples feel like they go on too long, including an Appendix of 60 pages of a replacement Date class for Java. I just find reading that much code in a book to be more difficult than on-screen.
3 of 3 people found the following review helpful:
5.0 out of 5 stars
This Book Changed Me,
By
This review is from: Clean Code: A Handbook of Agile Software Craftsmanship (Paperback)
I'd been programming for eight years in various languages and technologies when I read this book so I wasn't an absolute beginner; but after I read this book my coding completely changed, and I think for the better.
What impressed me most about this book was the many examples: "Uncle Bob" gave practical before and after examples of applying the principals of clean code. The examples were realistic and worthwhile: he'd take a piece of code, iteratively apply different principals and by the time he was done the code looked, well, clean, both in design and readability. From what I've heard, what people remember most is the principal of "self-documenting code". Now I too had heard all of that before and I'd seen some terrible "self-documenting" code; however, when Martin explained it--and gave examples--it began to make sense and I've been doing it ever since. Trust me, when _he_ explains it, it makes sense. The book goes well beyond self-documenting code. I would recommend this book for anyone who codes, but especially for someone with a couple years of, not just writing code, but also reading other people's code; often it's hard to pin down just what is so difficult and clumsy about the code we write and Martin shows us.
1 of 1 people found the following review helpful:
5.0 out of 5 stars
Great rules for long lasting code,
This review is from: Clean Code: A Handbook of Agile Software Craftsmanship (Paperback)
I am part way into this book and it's a great guide with specific examples on some best practices and recommendations on how To do and Not to for small and large code projects.
The writing style of the book is very easy to follow, and does not dry out with a sprinkle of geeky humor and real-life stories. The suggestions are based on the modern programming world today, and how the life of your code may last longer and go through more hands than you may expect. I have already started to change my coding patterns based on some of these recommendations.. and I know shifting my mindset over whatever period of time towards cleaner code, will benefit me and those to come after me. Clean Code should be standard for all programmers/architects/engineers in any position.
Share your thoughts with other customers: Create your own review
Want to see more reviews on this item?
|
Most recent customer reviews |
|
|
|