Assignments

This page refers to a lot of terminology that you have probably not seen before. Don't worry — we'll teach you what you need to know! You can also turn to the TA for help with these as needed.

Most assignments will be done in stages, in which we want you to complete (and commit to git) your work on one stage before we show you the tasks for the next. We'll do this so that you don't accidentally leak information to Claude about where the assignment is heading. In addition, we are simulating a common software engineering scenario, where new features are often suggested after an old one has completed, so you have to adapt rather than plan ahead. In addition, developing in stages is also an established software development practice.

Workflow for an Assignment

Getting Started

Completing Stages

When you have finished a stage:

Repeat until you have finished all stages.

Completing The Assignment

When you have finished all stages, submit the Assignment Completion Google Form. This will ask you for the URL of your research journal. After the first assignment, we will also have you update your chat transcript and information about your git commits.

The Assignment Links

Project 1: Due Monday Jan 27 by 10:00pm

Project 1.5 (Tetris dual): Due Thurs Jan 29 by 9:00am

Project 1.75 (Tetris tested): Due Mon Feb 2 by 5:00pm

Project 2 (Airport Weather): Due Wed Feb 4 by 7:00pm

Project 2.5 (Airport Weather more data): Due Monday Feb 9 by 7:00pm