One requirement for receiving credit for an assignment is the satisfactory completion of a code walkthrough. This page documents the procedures and expectations code code walkthroughs.
Scheduling
To schedule a code walkthrough, email the instructor or one of the CAs (see the Syllabus for their contact info) to arrange a time to do the code walkthrough during scheduled office hours. See Courselore post #2 for the office hours schedule.
A few points to be aware of:
- Please email at least 24 hours in advance; that way we will know to expect you, and it will help us handle situations where we are over capacity
- If you are working with a partner, both of you need to participate in the code walkthrough
- If you aren’t available for the entire duration of the office hour session, please indicate that (we will try to fit you in)
- We expect you to complete the code walkthrough within one week of completing the final milestone of the assignment
If you find that none of the scheduled office hour time slots work for you, please email the instructor so that we can work something out.
Expectations
In general, the purpose of the code walkthrough is for you to explain your work, and for us to learn more about your design and implementation decisions.
The code walkthroughs will be fairly information. We might ask you to explain
- how a specific function works
- the purpose of a specific commit
- a specific design decision
etc.
Evaluation
The result of a code walkthrough is one of two possibilities, Satisfactory or Unsatisfactory. Note that if you are working with a partner, each of you is evaluated separately.
In general, if you made a substantial effort to complete the assignment authentically, you should not have any difficulty in achieving a Satisfactory evaluation.