Methodology

  • Keep the course brief (80 pages or less for a 24-hour/8-lecture course).
  • Keep discourse to a minimal.
  • Give examples to a maximum.
  • Give simple examples. Do not include ‘clever’ tricks or non-standard code. Follow conventions and best-practices.
  • Give a single case example and build upon it throughout the lessons. As new skills are learnt through lessons, elaborate on this case example. Use no more than two or three inter-lesson case examples throughout the whole course. A single case example throughout the course would be best unless absolutely necessary to use more than one.
  • Leave room for plenty of lab work. Give plenty of simple easy-to-follow lab exercises plus a few more challenging ones for the more daring students.
  • Do not make an exhaustive list of all commands or a table listing all possibilities. If you find it absolutely necessary, then include such an exhaustive list in a separate appendix at the end of the book and refer to it inside the lesson.
  • When introducing a new concept or feature, let students first feel the need for this concept or feature. Then introduce this concept/feature as a natural solution for that problem or need. Give realistic problems or needs, never give superficial ones.
  • Use the bare minimum when giving code examples. Do not complicate things.
  • Whenever possible, use examples right away instead of expository when explaining new concepts.