Clean Code: A Handbook of Agile Software Craftsmanship – book review

Posted by DigiMortal on ASP.net Weblogs See other posts from ASP.net Weblogs or by DigiMortal
Published on Thu, 27 May 2010 19:09:00 GMT Indexed on 2010/05/27 19:11 UTC
Read the original article Hit count: 486

Clean Code: A Handbook of Agile Software Craftsmanship   Clean Code: A Handbook of Agile Software Craftsmanship
Writing code that is easy read and test is not something that is easy to achieve. Unfortunately there are still way too much programming students who write awful spaghetti after graduating. But there is one really good book that helps you raise your code to new level – your code will be also communication tool for you and your fellow programmers.

“Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin is excellent book that helps you start writing the easily readable code. Of course, you are the one who has to learn and practice but using this book you have very good guide that keeps you going to right direction.

You can start writing better code while you read this book and you can do it right in your current projects – you don’t have to create new guestbook or some other simple application to start practicing. Take the project you are working on and start making it better!

My special thanks to Robert C. Martin

I want to say my special thanks to Robert C. Martin for this book. There are many books that teach you different stuff and usually you have markable learning curve to go before you start getting results. There are many books that show you the direction to go and then leave you alone figuring out how to achieve all that stuff you just read about.

Clean Code gives you a lot more – the mental tools to use so you can go your way to clean code being sure you will be soon there. I am reading books as much as I have time for it. Clean Code is top-level book for developers who have to write working code. Before anything else take Clean Code and read it. You will never regret your decision. I promise.

Fragment of editorial review

“Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

What kind of work will you be doing? You’ll be reading code—lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.

Readers will come away from this book understanding

  • How to tell the difference between good and bad code
  • How to write good code and how to transform bad code into good code
  • How to create good names, good functions, good objects, and good classes
  • How to format code for maximum readability
  • How to implement complete error handling without obscuring code logic
  • How to unit test and practice test-driven development
This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.”

Table of contents

  1. Clean code
  2. Meaningful names
  3. Functions
  4. Comments
  5. Formatting
  6. Objects and data structures
  7. Error handling
  8. Boundaries
  9. Unit tests
  10. Classes
  11. Systems
  12. Emergence
  13. Concurrency
  14. Successive refinement
  15. JUnit internals
  16. Refactoring SerialDate
  17. Smells and heuristics
  1. A Concurrency II
  2. org.jfree.date.SerialDate
  3. Cross references of heuristics
  • Epilogue
  • Index

© ASP.net Weblogs or respective owner

Related posts about General Software Developm

Related posts about books