We are accountable for our actions and will act ethically and honestly in all our interactions.

Within the classroom, that means you do your own work! This is especially true when it comes to programming, as it is easy to copy another’s code. Copying code is cheating and lacks integrity. Such violations of cheating or plagiarism will result in zero to a full negative grade on the assignment and reporting to the appropriate university resources. Further infractions will result in an F given in the course.

CMU provides some nice examples to follow:

For personal assistance, here are some of the things that are appropriate:

• Clarifying ambiguities or vague points in class handouts, textbooks, or lectures
• Discussing or explaining the general class material
• Providing assistance with Java, in using the system facilities, or with editing and debugging tools
• Discussing the code that we give out on the assignment
• Discussing the assignments to better understand them
• Getting help from anyone concerning programming issues which are clearly more general than the specific project (e.g., what does a particular error message mean?)
• Suggesting solution strategies
• In general, oral collaboration is OK.

Here are some things that are inappropriate:

• Copying files or parts of files (such as source code, written text, or unit tests) from another person or source
• Copying (or retyping) files or parts of files with minor modifications such as style changes or minor logic modifications
• Allowing someone else to copy your code or written assignment, either in draft or final form
• Getting help that you do not fully understand, and from someone whom you do not acknowledge on your solution
• Writing, using, or submitting a program that attempts to alter or erase grading information or otherwise compromise security
• Copying someone else’s files containing draft solutions, even if the file permissions are incorrectly set to allow it
• Lying to course staff
• Reading the current solution (handed out) if you will be handing in the current assignment late
• Copying prose or programs directly
• Giving copies of work to others
• Coaching others step-by-step

If you do any of these, your should also acknowledge it in what you turn in; but expect to have a conversation with an instructor about it and, at least, suffer some penalty in the grade. If we discover you have done this and not acknowledged it, the penalty will be much more severe. In other words, dishonesty is much worse than stupidity.

Here are some gray areas:

• Reading someone’s code for clarity or bugs, after you have completed your own
• Helping with debugging
• Looking at someone’s prose or program but thinking about them and writing your own
• Following someone’s advice or instructions without understanding them
• Many others

These, too, should be acknowledged.

A few resources

• Cheating versus Collaboration
• CMU Policy
• CSU Resolution Center - Conduct Code