Week 4 Crit: Code
The same method, aimed at a pull request instead of a drawing --- proof that it wasn't an art-crit trick.
15 March 2027
Bring#
A small pull request or patch of your own — ten to eighty lines is the sweet spot, big enough to have a real decision in it, small enough to review in the room.
The crit#
Same silent-note-first structure as week 3, aimed at a diff instead of a drawing. “This could be cleaner” doesn’t survive here any better than it did on the drawing — the room’s standard question becomes “cleaner how, and what would convince you it already is.” Idris runs this one hardest, because he’s heard every version of a vague code review that still got approved.
Leaves with#
A review comment on a real diff that names the line and the failing case, not the vibe.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- your review comment references a specific line or function, not "the approach"
- you can state what test or example would show your comment is wrong
Teaching team
- Marisol Quaye — convenor
- Idris Fenn — tutor