The course-wide rules for late work, extensions, academic integrity and getting help.

Policies and support#

Weekly prototype work#

Each week’s studio exercise is built and tested in that week’s session, not assembled later from memory. Bring a working toolchain to every session — week 1 assumes nothing further has been installed in advance. A prototype that only runs on your own machine, or only in your head, does not count as built.

Collaboration and individual submission#

Talk to anyone about anyone’s prototype — comparing how two people solved the same week’s constraint is most of what a studio session is for. What you submit for marking, though, is your own: your own code, for your own sessions and vocabulary log. If a specific week’s exercise asks for a pair or a second player, that will say so in the exercise itself; the default is solo work.

Accessibility#

The one-button constraint is a design position, not an accessibility retrofit, but it does mean this course’s own exercises should be usable by someone who cannot reliably time a press to the millisecond or hold a key down for an exact duration. If a studio exercise’s timing windows or hold thresholds make it unplayable for you specifically, say so in the session — the fix is almost always a number, not a rewrite. Session rooms, decks and recordings follow the university’s standard accessibility provisions; contact the convenor if a specific week’s material doesn’t meet them.

Tools, code and assets#

Use whatever engine, library or framework gets a working prototype in front of you by the end of the session — the constraint is the single input, not the toolchain. Borrowed code, art or audio is fine if you did not write or draw it yourself, as long as you say where it came from, in a comment or a one-line credit alongside the prototype. Code generated by an AI tool is also fine on the same terms: say so, and be able to explain what it does when asked — a prototype you can’t explain isn’t yet yours to submit.

Late or missed studio work#

The vocabulary log is submitted as each week’s prototype is made, not assembled at the deadline, so a missed session shows up as a missing prototype rather than a late file. If you miss a session, build that week’s exercise before the next one and add a one-line note saying which session it covers. If more than one week goes missing, or a deadline for a larger piece of assessed work is close and won’t be met, contact the convenor before it passes, not after — a plan made in advance is almost always possible; one requested afterwards depends on the reason.