Notes On: ISYS-320 Online Delivery

• Start with same basic materials (written and lecture videos) as ISYS-600 Intro to prog
• Do togethers are very important
• Revisions after grading allowed
  • Fewer points for revisions as semester goes on
  • No revs at the end
• Feedback, feedback, feedback
  • Lots of written feedback
  • Early feedback on homeworks actually gives lines of code (giving answers) with explanations of why – demonstrating thought process not just the ultimate code
• "Seeing" the thought process is key
• Remove Gradient Bar from undergrad
  • Math problem as much as a programming problem
• Remove vending machine from undergrad
  • Processing so much of somebody else's code is a bit much
  • Particularly when they haven't created any classes for themselves yet
  • Remove adventure game – this is something I just decided to do with the on ground version
• Feedback with option to revise
  • Feedback early is actual lines of code with lots of "why"/thought process
  • Feedback slowly becomes less concrete and more "abstract"
  • Not lines of code, but "How did we see that done before? How can that be applied here with slight modifications?"