The homework presentations have the following general structure:
- The two partners must show up together at the schedule time.
- Each partner gets to present one piece of code for around 10 mins. See
- In general, the panelists will lightly direct your presentation or ask
pointed questions. Understand these questions as hints for where your
code is wrong, your presentation of the code is wrong, or both.
- For the last ten minutes of your joint slot, the panelists will
evaluate your code/presentation and present the evaluation to you.
- At this point, you must listen and you must take notes. Bring a note
book and a pen along; not doing so suggests we should take off additional
For each partner, the panelists will open the chosen solution in
A solution that runs and achieves 100% syntactic test coverage gets a
small fraction (say 10%) of the weekly score.
In addition, the panelists will check your code for basic stylistic
properties. See the style sheet for details.
Your code/presentation is evaluated at two levels: your code and your
presentation of the design decision according to the design recipe.
This part of the meeting accounts for a large fraction (say 80%) of the
The remaining fraction (around 10%) of the weekly score are "partner
points." If the two scores are too far apart (determined on a per problem
set basis), each of you simply get the average of the two scores. If the
scores are close, you also receive the partnership points. We fully
understand that this is not a perfect test of your pair programming