cs-106 — The Grade Typos
| Field | Value |
|---|---|
| id | cs-106 |
| difficulty | Foundational |
| topics | cleaning, boundaries |
| lecture | lecture-27 |
| estimated time | 5-minute attempt + 10-minute discussion |
| prerequisites | lectures 1-2 (problem framing, precise pseudocode) |
| objective | recognise the pattern, translate it into precise steps, and trace it correctly |
| solution | held by the instructor; discussed after the attempt |
Problem
Scores like 105, -3, 'eighty'. Categorise defects, choose a policy per category (fix, flag, drop), and defend each choice.
Your deliverable is the stated assumptions, the correction rules in priority order, and one record where two rules compete and you say which wins. If the problem is ambiguous anywhere, state the assumption you are making and carry on — a stated assumption is part of a good answer.
Examples
- Input: scores: 105, -3, 'eighty', 84, 92
- Output: policies: 105 -> flag (over 100, maybe bonus); -3 -> correct to missing (impossible); 'eighty' -> parse to 80 (known map); else keep
Solve for the worked instance first. Then ask what would change if one number, name, or condition were replaced by something stranger.
What to notice
- Each defect class gets its OWN policy: fixable, flaggable, or reject - and the policy is written before the code.
- Writing the rules IS the solution; code is transcription.
- Every assumption is a place where two good answers can differ.
Discussion starter
After the solution is revealed, the class spends five minutes on this prompt: "Which assumption would you attack first if you had to argue the other side?"
Constraints and assumptions
- Difficulty: Foundational (early-semester techniques assumed: precise statements, traces, simple loops).
- Topics: cleaning, boundaries.
- Classroom-scale inputs unless the problem says otherwise.
- Time-box: about five minutes; naming the pattern and stating the assumption is already a pass, completing the calculation is the stretch.
- Optional stretch (not required): describe an alternative approach and say when it beats the obvious one.
Hints and extension
- First nudge: identify the pattern the worked instance uses before computing anything.
- If stuck after three minutes, write the input/output line you expect and trace the smallest example by hand.
- After the reveal, attempt the extension below before the next lecture.
- Extension challenge: Draft the audit trail paragraph a reviewer would need to trust your cleaning.