Book Review: Clean Code: A Handbook of Agile Software Craftsmanship

Do you want to write just code or clean code ?

Good clean code isn’t easy to come. It needs practice, discipline and professionalism.

I remember seeing someone’s email signature – “Code as if the next programmer to read your code is a serial-killer who knows where you live.”

Bad code sets forth bad karma. You live with the consequences of what you do and others live by the consequences of what you do.

I am reading this must read book – “Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin Series)” by Robert C. Martin.

I will be posting quick summary of the chapters as I go through the book.

This will serve as an ‘index’  for other posts related to this book.  This in no way replaces the importance of reading this book though I hope it will re-enforce the need to read it.

To read more about what this book is about- see the review of the first chapter.

Chapter 1: Clean Code.
Chapter 2: Meaningful names
Chapter 3: Functions
Chapter 4: Comments
Chapter 5: Formatting
Chapter 6: Objects and Data Structures
Chapter 7: Error Handling
Chapter 8: Boundaries
Chapter 9: Unit Tests
Chapter 10: Classes
Chapter 11: Systems
Chapter 12: Emergence
Chapter 13: Concurrency
Chapter 14: Successive Refinement
Chapter 15: JUnit Internals
Chapter 16: Refactoring SerialDate
Chapter 17: Smells and Heuristics

And my closing thoughts are here.

Be Sociable, Share!

•