Assignments
Instructions for each assignment are posted when it is released. The dates below are for planning. Every deadline is also on the Course Calendar.
Dates at a glance
All deadlines are 11:59pm. Presentations happen at your team meeting. “Initial PR due” and “Final PR due” are two deadlines on the same pull request, not two separate PRs: you push new commits to it as you address review comments.
| Released | Initial PR due | Peer code review due | Final PR due | Presentation | |
|---|---|---|---|---|---|
| A1 | Wed 9/30 | Wed 10/7 | Fri 10/9 | Mon 10/12 | Mon 10/12 - Wed 10/14 |
| A2 | Wed 10/14 | Wed 10/21 | Fri 10/23 | Mon 10/26 | Mon 10/26 - Wed 10/28 |
| A3 | Wed 11/4 | Wed 11/11 | Fri 11/13 | Mon 11/16 | Mon 11/16 - Wed 11/18 |
How assignments work
There are 3 assignments, done in your pair. Each one follows the same steps. All deadlines are 11:59pm.
- Released. The assignment and your repo are ready.
- Initial PR due, 7 days after release. Open a pull request in your pair’s repo with your best work: your code, your documentation and diagram, and your process journal so far.
- Peer code review due. Review the PRs of 2 other pairs and leave your comments on them. Your pair also gets reviews from 2 other pairs. Your tutor sets who reviews whom, and it changes with each assignment.
- Final PR due. Reply to every comment on your own PR: fix it, or explain why you did not. Update your documentation, diagram, and journal to their final versions.
- Presentation. Present your final work at your team meeting and talk through the feedback with your tutor.
This is one PR per assignment, not two. You open it at the initial PR deadline and push new commits to it as you address review comments; “final PR due” is the deadline for those commits, not a second pull request.
Your tutor grades the final version of your PR, after you have addressed the code review. There is no resubmission after grading. Whether you acted on the feedback is also part of your collaboration grade.
Late work is not accepted. Each deadline stands on its own. Missing one does not make the whole assignment late.
- Miss the initial PR deadline: your pair is out of the peer review process, both giving and receiving. You can still submit at the final PR deadline and earn Technical and Communication, but your Collaboration score is 0.
- Collaboration has two parts: giving your 2 reviews, and addressing the comments on your own PR. Miss the reviews but address the comments: capped at 1. Give the reviews but do not address the comments: capped at 2. Do neither: 0.
- Do not submit a final PR: your initial PR is graded as the final version and your Technical score is capped at 2. If you also missed the initial PR, your Technical score is 0. Not addressing the review comments only affects Collaboration, not Technical.
See the Syllabus for the full policy.
A1 and A2 use idlelib and are done by hand. A3 uses an agent on OpenRefine, and the scope is larger. A1 modifies an existing feature and A2 adds a new one. A3 adds a significant feature to OpenRefine.
A1: Modify an existing feature
idlelib. Read the writeup
| Step | When |
|---|---|
| Released | Wed Sep 30 |
| Initial PR due | Wed Oct 7 |
| Peer code review due | Fri Oct 9 |
| Final PR due | Mon Oct 12 |
| Presentation and tutor discussion | Team meeting, Mon 10/12 - Wed 10/14 |
A2: Add a new feature
idlelib
| Step | When |
|---|---|
| Released | Wed Oct 14 |
| Initial PR due | Wed Oct 21 |
| Peer code review due | Fri Oct 23 |
| Final PR due | Mon Oct 26 |
| Presentation and tutor discussion | Team meeting, Mon 10/26 - Wed 10/28 |
A3: Add a significant feature, with an agent
OpenRefine
| Step | When |
|---|---|
| Released | Wed Nov 4 |
| Initial PR due | Wed Nov 11 |
| Peer code review due | Fri Nov 13 |
| Final PR due | Mon Nov 16 |
| Presentation and tutor discussion | Team meeting, Mon 11/16 - Wed 11/18 |
Group Project (counts double)
Groups of 5, assigned by your tutor. You work on OpenRefine with agents. This is a bigger project than A3: a multi-part feature or end-to-end change, with tests and documentation, that the group splits up and merges. Your group hands in a proposal and then starts on the project. Your tutor gives you feedback on your scope at the checkpoint presentation and may ask you to adjust it. The proposal is not graded. The Group Project is graded on two equal parts: the checkpoint presentation, and the final PR and presentation.
| Step | When |
|---|---|
| Released | Fri Nov 6 |
| Proposal due | Fri Nov 13 |
| Checkpoint presentation | Team meeting, Mon 11/23 - Wed 11/25 (Thanksgiving is Thu and Fri) |
| Final PR due | Wed Dec 9 |
| Final presentation, 3:00-5:59pm, FAH 1450 | Thu Dec 10 |
The proposal is short, about half a page: the issue or feature you will work on, your goal, your plan, how you will test it, who does what, and where you plan to use an agent.
The checkpoint presentation is about 10 minutes per group at your team meeting that week. Show what you have built so far (a short demo if you have one), your plan for the remaining time, how you used agents and checked their output, and the risks you see. Every member presents part of it. Your tutor asks questions for about 5 minutes and gives you feedback on your scope. It is scored 0-3 on the same rubric as the other presentations.
Your tutor sees your group at every team meeting.