Assignments

Every assignment arrives as your own private GitHub repository, created for you inside the course organization. Clone it and work in VS Code.

Your repository is checked automatically each time you push, and the tests tell you how you are doing. That score does not set your grade, assignments count as complete when you submit reasonable work, green tests or not. See Grading for how completion feeds into your final grade.

Before any of this can happen, you must send your GitHub username to your instructor and accept the invitation to the course organization, Getting Started walks you through it.

Assignments are grouped by the week they begin. Weeks carrying more than one assignment are marked with a heavier rule and a bold count, plan ahead for those.

Each assignment opens on the Monday of its week. You can see the whole term below, but a future assignment stays grayed out with its opening date until then.

Setup submitted, but not counted toward your grade Published open, ready to start Opens Oct 12 unlocks at the start of its week
Week 00 Aug 31 – Sep 5 2 assignments + 1 setup task
Week 01 Sep 7 – Sep 12 1 assignment
Week 02 Sep 14 – Sep 19 1 assignment
Week 03 Sep 21 – Sep 26 1 assignment
Week 04 Sep 28 – Oct 3 1 assignment
Week 05 Oct 5 – Oct 10 2 assignments
Week 06 Oct 12 – Oct 15 1 assignment
Week 08 Oct 23 – Oct 31 1 assignment
Week 09 Nov 2 – Nov 7 2 assignments
Week 10 Nov 9 – Nov 14 2 assignments
Week 11 Nov 16 – Nov 21 1 assignment
Week 12 Nov 23 – Nov 28 1 assignment
Coming soon
AVL Trees
Topic is set; the assignment opens before its week begins.
Weeks 13–14 Nov 30 – Dec 9 1 assignment
Tip

Each assignment page lists the skills it gives you evidence for. If your submitted work clearly demonstrates a skill, you don’t need a check-in appointment for it, see Skills & Check-Ins.