Guidelines, methods

• Shorter is better

  • Avoid long, unreadable code (hard to maintain and locate errors). Instead, split code into smaller functions
  • Each method should do only one job

• Comment your code

  • Write complete JavaDoc for all classes and methods
  • Describe why you do it, not what you do

• Handle errors

  • Trap errors if neccessary
  • Otherwise, pass errors to calling routine

• Program flow

  • Use function results to keep track of the code execution

Notes: