The fundamental rule for CSE260 is very simple: don’t cheat. Cheating robs you of a learning experience and unfairly disadvantages your peers. Instead of cheating, make use of the CSE 260 staff to help guide you in the mastering of the material. Cheating prevents you from actually gaining the knowledge and experience needed to succeed in this course and in your career following this course.
So really, don’t cheat.
What is cheating?
So what is cheating? First, make sure you have read and understood the UCSD Policy on Integrity of Scholarship . Take a moment to read it now. In computer science especially, the line between cheating and not cheating may seem vague. So we are trying to make it more explicit by stating what is considered cheating and what is not.
What are the specifics for CSE 260? In CSE 260, you can read books, surf the web, talk to your friends and the CSE 260 staff to get ideas for solving your programming assignment problems. DO NOT, HOWEVER, SEARCH for CSE260 assignments, solutions, etc. You can use generative AI for inspiration, but you may not copy code from generative AI. If you use AI as a resouces, you must cite it and provide the prompts/input used to genearte the result.
There is also a gray line between asking your friends for help who have previously taken this course. When in doubt, assume it is wrong and talk to us instead. You, or your 2-person team, must write your own solutions to your programming assignments. Using program code that someone else has written (unless they are in your team for that assignment, or the code was explicitly provided as part of the assignment), or providing program code to someone else not on your team, or turning in code that you have written with someone else not in your team, is cheating.
WRITE YOUR OWN CODE
To help ensure that there is no way you might be suspected of copying someone else’s code, we ask that you commit to your repository early and often. If you do regular commits, we will be able to see your progress and know that you are making progress on your own toward a solution. Be sure to include comments in your code, as well as in your commits, so we can follow the progression of your code. Doing regular commits helps maintain academic integrity.
Don’t even look at or discuss another student’s code, and don’t let another student look at your code. Don’t start with someone else’s code and make changes to it, or in any way share code with other students.
You must not copy code or content from genearated by a machine. If you use such code as a reference, you must provide the prompts/input used to generate that code or content
If you work with a partner, you should both be sharing in the work.
Also, in CSE 260, you must write your own answers on any test or exam. Getting answers from someone else, or providing answers to someone else, is cheating.
If you do cheat, we will enforce the UCSD Policy on Integrity of Scholarship. All suspected cases will be submitted the Academic Integrity office for investigation and resolution. Possible consequences are: you will get an F in the course, and the Dean of your college will put you on probation or suspend you from UCSD.
Note: all work code must be committed using classroom.github.com repository, and no other repository may be used. Use of other repositories or using github in a way that obscures development history raises Academic Integrity issues.
Note on 3rd party disclosures:
To detect instances of academic integrity violations (and protect us all) in programming assignments we will use 3rd party software. Including your name and/or PID in the source code will disclose that information to the 3rd party.