Assignments
Handouts are posted here as the semester progresses. Dates live on the schedule; the band requirements every assignment feeds live in the syllabus.
Everything in this collection is a draft until the semester begins. Dates and expectations may change.
| Assignment | Type | Due | Feeds |
|---|---|---|---|
| Code Review | Individual | continuous, Sep 17 – Dec 10 | Requirements at every band |
| Project Bids | Individual | Thu Sep 17 | Not assessed, required |
| Reading Bid | Individual | Thu Sep 24 | Not assessed, required |
| Declare Your Target Band | Individual | Thu Oct 1 | Sets what the checkpoints read you against |
| Team Workspace & Charter | Team | Thu Oct 1 | Not banded, required · read at Checkpoint 1 |
| The Ticket Hunt | Individual | Wed Sep 16 | Pass |
| Onboarding: Gradebook Column Groups | Individual | Thu Sep 24 | Pass · banded internally |
| First Implementation Ticket | Individual | Thu Oct 29 | Pass |
| Drill Zero: Async Triage Log (handout to follow) | Individual | Fri Oct 9 | Pass/fail |
| Async Sprint: Focused Learning + Team Sync | Individual + team | Tue Oct 13 | Pass |
| Checkpoints 1–3 (handout to follow) | Individual | Oct 14 · Nov 5 · Dec 3 | Pass |
| Reading Presentation | Pairs, one group of three | Oct 21 · Oct 28 · Dec 2 | Pass |
| Game Day Postmortems (handout to follow) | Team | within 48h of each game day | Pass · Credit |
| Feature Freeze (handout to follow) | Team | Mon Nov 23 | Distinction |
| Learning Summary Report (handout to follow) | Individual | Thu Dec 10 | The band claim itself |
How work is assessed
Nearly everything in this course is graded from natural artifacts, the things professional software work produces anyway. Pull requests, reviews, commit history, design docs, research notes, Discord threads, monitoring dashboards. There are very few artificial submissions.
That means when and how you work is visible, and it counts. Cadence, surfacing blockers early, and responding to review are assessed alongside what you shipped.
Each handout therefore ends the same way: an expectations table, then what strong and weak versions of the work actually look like. Read those two sections before you start, not after you finish. They are the rubric.