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

Policies and support#

Late work#

Each assessment loses 5% of its weight per day late, up to five days, after which it earns zero. The Hate Catalogue is the one exception: it’s a running document due at the end of week 3, and a late submission is marked as it stands the day it’s actually turned in, so it’s never worth padding it after the fact.

Extensions#

Ask before the due date, not after — email Marisol with what’s happened and how much time you need. Extensions are granted for illness, misadventure or documented hardship, not for having started late. A short extension for a good reason is easy; a long one needs paperwork the university requires anyway.

Academic integrity#

Every one of this course’s four assessments asks you to analyse and build around a design you didn’t create, which makes the line unusually clear: your account of why something works has to be your own analysis, not a paraphrase of someone else’s write-up of the same interface. Citing a source that pointed you at an example is fine and expected. Presenting someone else’s explanation of the mechanism as your own is not.

Use of AI tools is permitted for research, drafting and testing support, provided the analysis and design decisions are yours and you can defend them without the tool in the room — several assessments (the Hostile Design Experiment in particular) require exactly that kind of live defence.

Getting help#

Workshop questions — anything about the interface or object you’re currently building — are fastest resolved live in a session with Idris, in front of the thing itself. Course-level questions — extensions, grading disputes, anything that can’t wait until the next session — go to Marisol by email. If a question about specific feedback doesn’t get resolved by the person who gave it, escalate it rather than letting it sit.

Feedback#

Something about the site or the course not working the way you’d expect? Say so below.