The links below (some in bold) are ordered by what we think you'll be checking most often through the semester first! Hence, information unlikely to change throughout the semester, such as policies, are later in the list.
The course schedule, with links to lecture and assignment materials.
Need to reach us? Consult our office hours and staff contact info.
Four programming assignments (with possible partial milestones) (should be done in pairs, individual is OK) (each is expected to take tens of hours, but this time is distributed over multiple weeks) = 17% each; one evening midterm = 16%; one in-person final = 16%;
but, since the exams test conceptual, individual-level knowledge, to receive a C- or above in the course, students must receive at least a C- on both exams.
If you want to use git with your partner, you should use the Cornell COECIS GitHub, which allows you to create a private repository. Other versions of GitHub may make your private repository public without your knowledge.
If there is a need for a "group divorce" (some work was done jointly but the two of you no longer wish to work together), please contact email@example.com for further instructions.
Until all students' submissions' grades for the assignment have been posted (in case there are people with extensions and makeups) ...
(1) You must never look at, access or possess any portion of another group's program(s) in any form. (This includes lines of code written on a whiteboard, lines of code described verbally.)
(2) You must never show or share any portion of your program(s) in any form to anyone except a member of the course staff. As a consequence, do not post any part of your programs to Ed Discussions. (Posting error messages that contain snippets of code is OK.)
(3) You must not ask for or copy solutions from outside sources (such as StackOverflow or code autogenerators).
(4) You should specifically acknowledge by name all help you received, whether or not it was "legal" according to rules (1)-(3) above. This is also known as "citing your sources".
: you do not need to acknowledge the course staff (although we appreciate it if you do!).
Example: in an assignment file, the header could read "Sources/people consulted: discussed strategy for process_strings() with Claire Cardie and Hakim Weatherspoon".
If you turn in someone else's work for course credit, and forthrightly acknowledge you are doing so, you are not acting dishonestly and are not violating academic integrity, but that also does not show us you have learned anything. Thus, you may not receive grading credit, but you would not undergo academic integrity hearings. If, on the other hand, you violate academic integrity by claiming someone else's work as yours or by giving unauthorized help, then the academic integrity hearing process will be triggered, which can incur both grade penalties and storage of records by your College. For more on Cornell's policies and procedures, see the Dean of the Faculty's Academic Integrity Website.