The following are hidden (display:none)



  1. Parson's problems were fun
  2. Parson's problems lead to good discussion
  3. Parson's problems were faster / easier than 'write code from scratch' problems
  4. Effective use of color in the slides was helpful in understanding stuff


  1. Parson's problems were very picky (indentation)
  2. Parson's problems were unable to accept alternate, valid, answers (var x; var y; must be declared in the correct, arbitrary order)

My Take:

  • Essentially, it's a way to get them to look at an example in detail. 
    It's interactive, it forces them to look at things closely, and it takes less time than coding it up by hand.
  • It is a bit of a stickler (and there's no obvious, easy way to allow for multiple, correct versions)
  • It may be tedious over time (after the initial 'ooo!  fun!' wears off)
  • Better for covering stuff near the start of the quarter, rather than at the end

More ideas:

  • Storage & retrieval
    • Add new items to the end of the array, then list or search them?
  • parallel arrays?
    • grades & names
      • print matching
      • print highest/lowest
    • detect palindrome?

Paste next section here