well demo isn't exactly required. its not realistic to have 82+ students demo their code to one person. i think that instead, you are supposed to include comments in your code on every line to show that you understood the program.

Lab1's due date was delayed for various reasons. From now on, including Lab 2, the labs will be due at the end of the week.

WRT demoing, what we're really talking about is reviewing. In most companies a developer is required to have his/her code reviewed by a co-worker before it is checked into the product archive. The review should include reading and discussing the code as well as running some example test cases. Peer review is one way to maintain quality. I want you all to do that. In addition, I think it's useful for the reviewer to look at someone else's code. You will see how someone else thinks, which will often give you ideas about how to improve your work.

If you can't get your code reviewed in the lab, exchange email address or other communication mechanisms so that you can get it reviewed afterwards.You might post your code to GitHub, Google Docs, Dropbox, or some other source where it is accessible to others.Then you and the reviewer can talk while you both have it in front of you.