How to improve the craftsmanship of software developers

Ch1 - Intro

• boy scout rule
  • leave code cleaner than you found it

Ch2 - Naming

• naming convention document

Ch3 - Functions

One of the more universal, yet simple rules is: Function names should be verbs if the function changes the state of the program, and nouns if they're used to return a certain value.

• small (4-10 lines)
• does only one thing
• have at max 2 arguments

Ch4 - Comments

Ch5 - Formatting

• vertical alignment, you don't want to scroll right
• most important functions at top of code
• team formatting rules