Learning to plan your time on complex software projects is an incredibly important skill in geek life, and that goes double for tackling unfamiliar tasks. However, even the best intentions do go awry once in awhile, and some programming assignment takes you longer than expected. For these rare and painful scenarios, there is a "late policy" for programming assignments in this course; this means that for programming assignments (only), it is possible to turn them in late and still receive at least some credit.
The programming assignments in this class are quite compact in nature, meaning that the total time to do them is relatively small, so that even having an extra hour or two give significant advantage. Plus there are often "timed challenges", meaning that I release a set of test data for you to run shortly before the due date. Persons who turn programs in late receive unfair advantages over classmates in both of these respects, so that penalties for late work must be significant enough to strongly encourage good time management and on-time submission.
The following table summarizes the late work penalty policy for programming assignments in this course. This policy applies specifically to programming assignments; the late policy for other class work is shown in the syllabus (usually: no late work accepted).
| Given that the due date is at time T: | ||||||||||
|
The way it works is as you'd expect: I grade the late assignment just I normally would and determine its score. The above-listed penalty percentage is then subtracted from this score.
Example: 100pt program due at 11:30am in class. You turn it in at 3pm; that falls in the -20% range. I grade the assignment and you score a 95. Recorded score= 95 - (95*0.2)= 76
To submit a late programming assignment, you should email me the code for the assignment. Make sure the subject line clear states the assignment and that it's a late work submission. The timestamp of the email in my inbox will determine the official submission time for penalty calculation purposes, and this is the version that will be graded.
Note that, if hardcopy submission was originally required, you will still need to submit the specified hardcopy packet at my office by start of the next business day. The emailed version just stops the clock, and establishes the official version to be graded (and of course it would be academic dishonesty to later submit a further-developed hardcopy).
Again, this whole process is designed only a life-ring to use only as a last ditch effort to save a time-planning disaster. It's much better to just get your work well in advance of the due date!