Last updated: Wed, 7 Jan 2015 16:16:48 -0500
Your final grade for the course will be computed from the following:
There is no midterm or final exam in this course.
Homework determines the bulk of your grade (~90%).
There will be a homework assignment each week and you will receive a weekly grade. Your weekly grade will be determined by a combination of automated tests and code walk presentations. See the Homework Policies page for additional details about homework.
Each homework assignment may have a different weight. Your final grade will be determined by computing a weighted average your homework scores. The weight of each assignment will be determined at the end of the semester.
To accomodate special circumstances that arise during the semester, we drop the lowest homework grade.
We will occasionally have quizzes during class to check basic understanding of course principles. Quizzes constitute a small portion of your grade (~5%).
The remainder of your grade (~5%) is determined by the course staff.
This portion of your grade is determined by all other activities in the course, such as class participation or helpfulness on Piazza.
submitted within 7 days of receiving your grade,
a private Piazza Note to all Instructors,
includes your partner if working in pairs,
tagged as "Issue_ticket".
In addition, a complete Issue Ticket contains the following information:
your full name,
your ccs account name,
a link to your github repository,
your partner name (if applicable),
your code walk time and location,
your code walk TA’s name,
the number of points in dispute,
Improperly formatted or incomplete tickets will be ignored.
Supporting evidence may be taken from course reference materials, Piazza posts, or class discussions.
Note: Submitting an Issue Ticket opens your entire assignment submission for re-grading. Thus, your score may go up or down as a result of an Issue Ticket.
Issue Tickets are discussed during our weekly staff meeting and may take up to seven days to resolve. A closed issue ticket will have "Resolved" in the title and will not be monitored by the staff. Start a new ticket if you wish to continue discussing a resolved ticket.
Here is an example of a proper Issue Ticket:
Summary: Issue :: Double Decomposition
Here is a list of commonly submitted improper Issue Tickets, phrased in a question-and-answer format. Any Issue Tickets resembling the following questions will be ignored.
Q: I lost a large number of points due to one small typo. That is unfair. May I fix just one character?
A: We grade all homework as they are submitted. You may not fix any typos.
Programming is a precise activity. One misplaced character changes a program from 100% right to 100% wrong. And such small errors often have large consequences in practice.
In our years of experience, good programmers and good students simply do not make this kind of mistake. Thus, the loss of points is fair. In fact, to allow fixing of typos would be quite unfair to those students who double-checked their work and wrote sufficient test cases so as to prevent these silly errors.
Q: I lost a lot of points because my solution is extremely sloppy and incomprehensible, but in my opinion it’s only very incomprehensible. Can I have some points back?
Q: I have to do well in this course. Can I have some points back?
Q: Other students were returned points for reason <X>? Can I have some points back for <unrelated reason Y>?
Q: I lost points for reason <X> in my code walk, but some other students with similar code did not. Can I have some points back?
A: No. Your code walk grade depends not only on your code, but how effectively you communicate what you did. Thus two students with the same code may receive different scores.