Clean Code – Chapter 1 Summary

Robert Greiner a number of years ago posted a trio of books that were a defacto for developers to read.

http://robertgreiner.com/2013/09/software-developer-book-recommendations/

I am starting with clean Code Chapter 1.

The Qualities of Clean Code

• Bjarne Stroustrup
  • Elegant
  • Efficient
  • error handling complete
  • performance close to optimal
    • as to avoid temptation to make the code messy
  • does one thing well
• Grady Booch
  • is crisp, isn’t obscure
    • reads well
• Dave Thomas  (OTI)
  • Testable
  • Easy to maintain
• Michael Feathers
  • the code looks like it was built by someone that cares about the code
• Ron Jefferies
  • Runs all the tets
  • contains no dups
  • minimizes the # of entities
  • expressiveness – tiny abstractions
• Boy Scouts rule: Leave Campground better than it was. Apply to code.