Clean Code Chapter 1

• What is Clean Code?
  • Bjarne Stroustrup, Inventor of C++
    • Wasted Cycle are inelegant, not pleasing
    • Error handling should be complete
    • Focused; Each function, class, and module expose a single-minded attitude that remains entirely undistracted, and unpolluted, by the surrounding details
  • Grady Booch, author of Object Oriented Analysis and Design with Application
    • He took a readability perspective
    • Well-written purpose
    • clean code should clearly expose the tensions in the problem to be solved
    • Should be matter-of-fact as opposed to speculative
  • Dave Thomas, founder of OTI
    • Make it easy for other people to enhance it
    • Code without test is not clean at all
    • values code that is small, code should be literate
  • Michael Feathers, author of Working Effectively with Legacy Code
    • Looks like it was written by someone who cares
    • Someone has taken the time to keep it simple and orderly
  • Ron Jeffries, author of Extreme Programming Installed and Extreme Programming Adventures in C#
    • No duplications
    • Express all the design ideas
      • High expressiveness
    • Minimize the number of entities
      • Find things in a collection
      • Wrap particular implementation in a more abstract method
  • Ward Cunningham, inventor of Wiki, inventor of Fit …
    • read turns out what you expected
    • make it look like the language was made for the problem
    • It is the programmer that makes the language appear simple
  • Author: Robert Cecil Martin
    • Discovering new techniques and founding their own schools

Many Recommendations in this book are controversial.

And we are AUTHORS.

• Making it Easy to read makes it easier to write
• The code has to be kept clean over time

This book cannot promise to make you a good programmer.

“Practice, son. Practice!”