Policies
Assignment Submission Policy
All assignments must be submitted on GitHub in order to be graded. The setup instructions walk you through the required steps.
Programming assignments must be submitted to student’s GitHub repositories by 11:59PM of the deadline date or will be considered late. Programming assignments that do not compile on the GitHub actions continuous integration system will receive a 0.
Late Policy for Assignments
For programming assignments, students are given four “slip” days for the entire semester. These slip days can be used one at a time or all at once. Upon consumption of these slip days, students will be assessed a -25 point penalty per day late.
Critically, there are no further extensions on programming assignments beyond the slip days everyone gets. If you run out of slip days, you will not be granted any more regardless of the circumstance. Make sure you save your slip days for when you truly need them, as you will not be given any more if you use them poorly. It is a limited resource.
Problem sets will be accepted one day late with a late penalty of -25, and there are no extensions beyond that.
Due to the nature of the paper discussions, you must submit the pre-class questions prior to the class meeting where the paper is discussed, and the in-class questions at the end of the class meeting. There are no extensions or makeups for the paper discussion questions.
If you have a serious, life-altering event occur that will make it difficult to complete the coursework, we strongly encourage you to contact Campus Support and Intervention to learn about what University-provided options may be available to you.
Exam Makeup Policy
For the midterm exam, if you have a documented emergency that prevents you from taking the exam as scheduled, please let your professor know as soon as possible.
Occasionally, the exam may conflict with a major conference that several students are attending such as Grace Hopper. In this case, let your professor know at least two weeks prior to the exam date and we will figure out an alternate time for the exam for affected students.
Under no circumstances will students be allowed to take one of the exams online.
For final exams, we are required to stick to the official University policy:
No student is permitted to omit or take early a final examination and no instructor is authorized to permit a student to do so.
Students should plan in advance to avoid scheduling conflicts in their final examinations. If a student is scheduled for two final examinations at the same time, the student should request to take one of the examinations on a different day or time. If a student is scheduled for more than two final examinations in one day, the student may request to take one of the exams on a different day or time. In either situation the student must contact the professors involved no later than two weeks prior to the scheduled examination date and request an accommodation.
That being said, if you have a documented emergency that prevents you from taking the final exam as scheduled, we will make a good-faith effort to schedule a makeup. However, there is a nontrivial chance you will have to take an Incomplete and make up the exam in a future semester.
Plagiarism and Individual Work Policy
In this class, assignments are expected to represent the individual effort of each student. All programming assignment submissions will be compared with current, previous, and future students’ submissions using MOSS, which is a code plagiarism identification program. If your code significantly matches another student’s submission, you will be referred to SJACS with a recommended penalty of an F in the course.
It is okay to discuss solutions to specific problems with other students, but it is not okay to look through another student’s code. It does not matter if this code is online or from a student you know, it is cheating. Do not share your code with anyone else in this or a future section of the course, as allowing someone else to copy your code carries the same penalty as copying the code yourself.
Furthermore, do not post your source code for the assignments on any public website including a public repository on GitHub. If you would like to share your source code with a potential employer, you may do so privately, but if you make your source code publicly accessible there is a high likelihood that someone in a future semester will copy your code.
Finally, using an AI such as ChatGPT to help complete any coursework (including assignments, labs, and exams) for the course is also an academic integrity violation and will be handled as such.
Course Material Policy
Do not reproduce, distribute, or post any lecture material, assignments, assignment solutions, or exams publicly without written consent of the instructor. You may take notes and make copies of course materials for your own use. You may not post course materials on sites like CourseHero or Chegg. Doing so is a copyright violation and in some cases may also be an academic integrity violation that will be dealt with accordingly.