Deadline for weekly tasks
The deadline for weekly tasks is Friday 1600, i.e., the lecture slot start time. Work done after that time (e.g., code committed after Friday 1600) will be credited for the following week.
It's OK to make occasional mistakes in weekly tasks. Making mistakes is a natural part of learning new things, after all. If a weekly task was not accepted as 'done' due to a mistake you made, go ahead and rectify the mistake as soon as you can -- in most cases, our grading scripts will not penalize such mistakes if they are corrected soon after.
We won't wait forever, though. Note that for most interim deliverables, we stop checking about one week after the deadline has passed. So, work/corrections done more than one week after the deadline might not get noticed at all by our grading scripts, even as late submissions.
Timing recommendations
- Start Weekn+1 tasks on Weekn Friday. As the Weekn+1 briefing is held on Weekn Friday (i.e., ~2 days before the week actually starts), we recommend that you start Weekn+1 tasks on that same Friday. That way, you have more time to finish them by the Weekn+1 deadline (i.e., Weekn+1 Friday 1600).
- Before attempting weekly project tasks, go through the weekly topics (and do the weekly programming exercises/activities, if any) because the knowledge from those topics may be needed to complete the project tasks.
- Try to finish most weekly tasks before attending the tutorial of that week, because some tutorial tasks are most useful after you have completed the weekly tasks.