Academic Honesty Policy
One of the (many) goals of this course is for you to become a better programmer. The only way to become a better programmer is to write a lot of programs.
In line with this, we require that any work you submit be entirely your own.
You should read this entire policy. Here are the three most important points, however:
- Write your own code.
- Never look at another student’s code.
- Never allow another student to look at your code.
This is a non-exhaustive list of things considered cheating in this course:
- Receiving code-level assistance from any person not an instructor or teaching assistant with the current semester of the course.
- Copying or stealing any amount of code from someone currently in the class or someone who has taken the class before.
- It does not matter if the code is provided electronically, visually, audibly, on paper, etc.
- Providing code you have written for an assignment to anyone else.
- Never share your code with others, including electronic sharing, showing someone code on your computer, verbally speaking the code, or writing down the code on paper.
- Finding code online and using it in the assignment
- Exception: you may use code from the course website. Please include a citation with a link when you do this.
- Putting code solutions from the course assignments online, even after the semester.
- Receiving code-level assistance from any person not an instructor or course assistant with the current semester of the course.
- Getting someone else to write some or all of the assignment code for you.
- Asking questions about the assignments on any online services except the course Piazza.
- Attempting to ‘hack’ or decompile the autograder to produce solutions. (If you want to do this for fun, let the instructor know. I can set you up with something to play with.)
- In the case that you have taken 15-112 before, copying your own code from a previous time you took the course. You are required to solve the problems again without referencing your previous solutions.
2.2. Quizzes and Exams
- Referring to any external resources while completing the assessment (phones, notes, other people, etc.).
- Copying part of an answer off of another student’s paper, even if it is very small.
3. Tutors, Friends, and Family
I am aware that some students receive help from outside sources in order to help them in the course. In some cases these people are friends (from CMU or not from CMU), family members, or privately hired tutors. For the purpose of this policy, all of these people are consider outside tutors.
If you have an outside tutor you may use them for any of the following:
- Help studying for quizzes.
- Help studying for exams.
- General help with learning to program and problem solve.
Use of tutor in any other way is a violation of this academic honesty policy. This includes, but is not limited to, the following:
- Help with the homework in any way. (Including any and all discussion of it.)
If you have any questions about use of an outside tutor, contact the instructor for clarification.
Note: You may discuss the homework with fellow classmates who also taking the class at the same time as you. See below for more details.
4. Good Collaboration
When working on homework, you are allowed to collaborate with other students in the course in the form of talking about the assignment together. The basic idea here is that you are encouraged to discuss the assignment together, but you should write your solution by yourself.
Here are some examples of healthy ways you could collaborate:
- Talk about the homework problems and discuss potential, high-level, approaches to solving them.
- Discuss ideas for useful testcases.
5. Bad Collaboration
You should never look at another student’s code or allow another student to look at your code. You are responsible for ensuring you do not look at another student’s code and that no other students look at yours. You also need to be careful to make sure that you are not “short-circuiting” the learning process for each other by over-explaining ideas and robbing other students of the ability to learn by experience.
Here are some examples of bad collaboration that is academic dishonesty:
- Having another student to look at your code to help you debug your program. (Or, helping another student debug their program by looking at it.)
- Working together to write pseudo-code (or code) that solves a problem.
- Looking at any part of another student’s code or allowing them to look at your code. Even a little bit. Even for just a second.
- Talking through a solution in detail.
6. Dangerous Collaboration
There are certain things students tend to do that inevitably lead to academic dishonesty occuring, and as such we strongly discourage you from doing them:
- Working near each other and talking about the homework while you are writing your code.
- Asking the same student for help every time you get “stuck”. (Or always helping the same student over and over again.) In this case, head to office hours instead.
7. Foolish Collaboration
Sometimes students share code by accident or without thinking about it. Here are some annecdotes to consider:
- Don’t post pictures that include your code to social media. That Instagram photo of you with your laptop that happens to have your code open might get used by someone else…
- When your friend emails you near the deadline and says “Hey, I finished the homework and got 100%! I feel great. Can I look at your solution so I can see how someone else did it?” What they really mean is, “This is due tomorrow and I don’t know what I’m doing. I’m going to message my gullible friend and trick them into sending me their code.” Even after the deadline you shouldn’t do this, because you never know if that student worked out an extension with the instructor.
- Your friend might come to you in tears because the homework is due soon and they haven’t solved it and if they fail then…
… their family with disown them
… they’ll be forced to leave the university when they fail the class
… they’ll be forced to leave the university when they fail the class and then sent back to their home country
… they’ll lose their scholarship
… other very horrible situation
So please can’t you help me!
Usually these claims are exaggerated, even if only in the student’s mind. Even if they aren’t, the situation is complex enough that it isn’t wise for you to try and figure out what is best for that student. Encourage them to see their academic advisor and/or the instructor to discuss their situation. The faculty members are in the best position to be able to help. We don’t want to see students fail and get sent away, either. If you give them your code, they’ll definitely fail (for academic dishonesty) and this time they’ll take you with them.
- Sending someone a copy of your solution after the deadline. That student
might have an extension that you don’t know about, or they may give your
code to someone else that turns it in during a later semester.
Penalties come from the course instructor and are decided based on the severity of the offense. Here are some past examples:
- Receive a -100% on the assignment.
- Receive a full letter-grade reduction in the course.
- Fail the course automatically.
A letter will also be sent to student affairs, which in the case of repeat offences may lead to further penalties such a suspension or expulsion.
9. Plagiarism Detection
We will look for cheating using both automated and manual means. If you copy code, we will find you.
10. Regret Period
Sometimes people make mistakes. Sometimes they regret them. We’ve all done stupid things and wished we could take them back.
If you commit an academic integrity violation on the homework, but bring it to the attention of the course instructors and have an open and frank discussion about it within 48 hours of your submission, we will allow you to withdraw the submission with no further action taken beyond that. An individual student may invoke this policy at most once during the course.
Parts of the policy come from Kelly Rivers and 15-112 in Pittsburgh. The regret period is adapted from “Teaching Academic Honesty in CS50” by Malan et al.