The bonfire crit

Why a closing critique session should be judged like the genre it studies — legible failure, not politeness, and not demolition either

A crit session run purely on encouragement teaches nothing a rejection teaches; a crit session run purely on demolition teaches nothing a compliment couldn’t have said faster. This course has spent eleven weeks arguing that a well-designed failure is legible — the player can name the exact decision that caused it — and a closing crit should hold itself to the identical standard. Feedback that says a one-pager “doesn’t work” is the cheating case: a bigger number (harsher tone) standing in for actual information. Feedback that says which specific part of the map sketch contradicts the item descriptions is the punishing case: it costs the presenter something to hear, and it tells them exactly what to fix.

The closing address at a bonfire crit — this course’s version of a send-off — is not a summary of the semester’s content. It’s closer to kindling a fire that’s about to go out on its own: the twelve weeks of scaffolding (lectures, workshops, spec checks) end here, and whatever judgment a student has built up about legible versus arbitrary difficulty has to now run without them. The point of naming that plainly, rather than letting the course just end, is the same point minimal UI makes about a HUD: the scaffolding was only ever there to build a habit of attention that should outlast the scaffolding itself.