Appearance
Assignments
REFLECT Forms: For each assignment, please fill out the associated REFLECT form linked below.
| Assignment | REFLECT | Assignment Quiz | Release Date | Due Date | Grace Period | 10% Penalty Period | 30% Penalty Period | Assignment Quiz Due |
|---|---|---|---|---|---|---|---|---|
| Assignment 1: Blockly | Inside Assignment | No Reading Quiz | 1/08 | 1/22 | 1/23 | 1/24-1/25 | 1/26-1/29 | 1/22 |
| Assignment 2: Faces | Reflect Form | Reading Quiz | 1/20 | 2/05 | 2/06 | 2/07-2/08 | 2/09-2/12 | 2/03 |
| Assignment 3: Turtles | Reflect Form | Reading Quiz | 2/05 | 2/19 | 2/20 | 2/21-2/22 | 2/23-2/26 | 2/17 |
Assignment Submission:
- All assignments are due by 11:59 pm ET on the specified due date.
- Submission instructions will be provided with each assignment.
Late Submissions:
- Submissions after the due date are subject to penalties, as outlined in the course syllabus.
- If unforeseen circumstances hinder your course progress, please fill out the extension request form).
Regrades:
- If you believe there’s an error in grading (be it a lab, apt, or assignment), submit the regrade request form within one week of the grade being posted.
Starter Code:
Some assignments come with initial code. This could be:
- Pre-completed files you’ll use without altering.
- Files with functions done or partially done for you to complete.
Comments will guide you on which code sections to adjust and which to retain as-is.
Code Style:
- A portion of your grade depends on your program’s readability, including style, comments, and variable names.
- Each modified Python file should have a comment at the top, detailing your name and netID.
- Additionally, provide comments for each function and significant code segment.
- Use descriptive variable names: for example, “totalCost” over “x”.