Please make sure you’re aware of the following course policies related to programming assignments.
Useful CSE 122 Resources¶
- CSE 122 Code Quality Guide
- CSE 122 Commenting Guide
- Tips for Testing
- Tips for Success at UW
- Java Cheat Sheet (ignore section on
ArrayList, “Access, Enacpsulation, and Static Methods”, “Inheritance and Polymorphism”, “Two-Dimensional Arrays”)
Note: Unless otherwise noted, all assignments are due at 11:59 pm Seattle time. If you have trouble submitting an assignment and the deadline is approaching, you should email all the files to Miya or your TA BEFORE the deadline so we have your submission on record. Submissions after the late cutoff may not be accepted even if there were technical difficulties turning in the assignment if you did not email us your solution before the cutoff.
Programming Assignments will be posted here as they are released.
P3 - Program Linting
Initial Submission by Thursday 03/02 at 11:59 pm.See Details
P2 - Absurdle
Initial Submission by Thursday 02/16 at 11:59 pm.See Details
P1 - Music Playlist
Initial Submission by Thursday 01/26 at 11:59 pm.See Details
P0 - Warm Up
Initial Submission by Thursday 01/12 at 11:59 pm.See Details
Revision and Resubmission¶
Once per week, you may revise and resubmit a previous Programming Assignment or Creative Project to demonstrate improved mastery. Your resubmission will be graded and the new grades will fully replace your previous grades. (Note that this means your grades may go down if you introduce new errors.) See the full policy in the syllabus for more details.
While feedback from your previous submissions is an important starting point for improving your work, addressing the feedback you receive does not guarantee any particular result on your resubmission. We will make every effort to provide feedback on all areas that could be improved, but oversights may occur. In addition, changes to address one area of feedback may introduce new errors or concerns in other areas. It is your responsibility to ensure that your work meets all expectations. Be sure to consult not only your feedback, but also the assignment specification, code quality guide, and other course resources and materials.
To resubmit a revised assessment, follow these steps:
- Make any desired revisions directly in your assessment in Ed and click Mark. As with your initial submission, you can make changes and click Mark as often as you like.
- Fill out a Google Form to tell us which assignment and which submission on Ed you want us to give new feedback on. You will need to provide the Ed submission number you would like to use. You will also need to to provide a description of the changes you made from your last submission. (Failure to do so will result in your resubmission not being accepted.) Each week, a new Google Form will be sent via email on Ed for you to make your resubmission that week.
You must complete both steps for your resubmission to be considered complete. Resubmissions in Ed in will not be graded unless the Google Form is also filled out correctly. If you are having difficulty accessing the Google Form, try following these instructions.
The resubmission period for each week runs from Wednesday to the following Tuesday. Resubmissions must be received by Tuesday at 11:59 pm to be considered for that week. You may only make one resubmission per week, though you may change which submission or which assessment you are resubmitting throughout the week by modifying your responses in the Google Form. Resubmissions received each week will be graded and feedback will be released by the end of next week.
If you think there was a mistake in our grading of your work, you can use the form below to submit a regrade request. This is not the same as a resubmission. One of the head TAs and/or Miya will regrade your previous submission and you will get an email from one of us with information if your grade on the assignment changed. Please use this form here.