Audience

1. Everyone who asks a question: state your name in the first sentence.

   (This is critical for Evaluating a Panelist.)

2. A panelist may interrupt a presenter at any point.

3. An audience member must raise their hand to ask a question.

   (The instructor will call on the audience members in order.)

Each audience member will provide to the instructor, via means to be specified, two documents, one per each presenter per panel. You should not include your name in anywhere in or on this document. That document should give the presenter:

1. Your own assessment of the grade you would give that presenter’s presentation

2. A brief summary of your reasoning for that score and/or things to improve.

3. Any additional notes about their code that we did not get to address in class.

Your submissions here are graded for completion. I will forward these on to the presenters en masse. I will, however, spot check them for quality and to ensure all communication is on point and constructive.

Practice It is encouraged to practice code walks with another pair.

But do not use work-in-progress code for practice reviews.

The goal is to practice technical explanations, questioning, and reacting properly to questioning. So there is no need to use code that you still have to submit. Doing so will only create the danger that you accidentally copy code. And you don’t want to do that.