The basic rule for CSE 260 is: don’t cheat. Instead, make use of the expertise of the CSE 260 staff to learn what you need to know to really do well in the course. If you cheat you will not become a better programmer, and you will not be hired or succeed in your job. So really, don’t cheat.
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.
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. However, 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.
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.
If you work with a partner, you must engage in true pair programming, as specified in the pair programming guidelines. That is, you and your partner must both physically present at the same computer anytime you are working on the assignment. You may choose to follow the full Extreme Programming model, but the important part for the sake of Academic Integrity is the pair programming practices.
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. 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 UCSD’s GitLab repository, and no other repository may be used. Use of other repositories or using GitLab in a way that obscures development history raises Academic Integrity issues.