Specifics for Secretaries
When you are secretary you are responsible to get a copy of the written notes to the section TA within 12 24 hours. Once the report is acceptable to the section TA, the instructor will grade it and get it forwarded to the reviewed pair.
the presenters
the panelists
the title of the project presented
the date and time
an bullet list enumeration of problems discovered:
Describes those problems in enough details so that the presenters can reconstruct it.
Describe the problems in terms of code, not in terms of what the presenters did.
You may offer suggestions of how to fix problems, but label them as such.
It remains the task of the presenters to fix the problems.
If the panel discussed potential solutions with the presenters, you may include these suggestions with the appropriate bullet item. You don't have to.
Email the memo as an HTML attachment to the section instructor.
The evaluation of a memo will take into account the timely delivery of the first draft, its format, its information content (focus on problems), and basic English writing (typos, grammar mistakes, incomplete sentences). The latter will affect your grade in a serious manner if the mistake allows a misinterpretation of a sentence or if the mistake makes an interpretation extremely difficult.
The phrase "first draft" implies that the instructor may give
you a chance to fix your submission and thus earn a grade before it
goes to the presenters. Those will appreciate a fast turn-around
time—
Alternatively, and to make it code-clear, the protocol diagram below specifies it all in gory detail.
|
STUDENT SECTION TA INSTRUCTOR |
|
---------------------------------------------------------------------------------- |
|
sit on panel |
take notes |
|
turn notes send to section TA checks |
into memo --------------------> basics |
|
|
forward to instructor reads, |
response 1: OK -----------------------> evaluates |
cc student |
|
xor |
|
response 2: |
request for fixes |
<=================== feedback |
|
fix basics send to instructor reads, |
double check ---------------------------------------------------> evaluates |
|
|
evaluation, requests for changes |
plus instructions to section TA |
<======================== <======================== |
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 practie 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.