Week 5 Lab: Assignment 1 clinic
A work session for Assignment 1, run as one-on-one check-ins rather than a taught lab, in the week the assignment is due
25 March 2027
Before the lab#
Bring whatever state Assignment 1 is in, running. There is no lecture content this week — the room is work time, cut into short one-on-one slots.
In the lab#
Book a slot when you arrive. Each check-in starts the same way: show your worst input, the one your build handles least gracefully, before anything else. That ordering is deliberate — a build’s edge cases are more diagnostic of what it actually does than its best-case demo, and clinic time is short enough that starting with the interesting part matters.
Outside your own slot, work on the submission. Two students comparing notes on the same failure mode, independently, is common and fine; two students with the same code is not, and it tends to be obvious in the check-in when neither can explain the part that’s supposedly theirs.
Afterwards#
Assignment 1 is due at the end of this week — see the assessment page for the exact time and what’s marked. There is no extension built into next week’s content for late submissions; if you need one, ask before the deadline, not after it.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you arrive with a build that runs, even if it's incomplete
- you can point to the specific input your build handles worst, without being asked to demonstrate it
- you leave with a written note of the one thing you changed as a result of the check-in, or a written note that nothing changed and why
Teaching team
- Callum Voss — tutor