The basic rule for CSE 100 is: Don't cheat. Instead, make use of the expertise of the CSE 100 staff to learn what you need to know to really do well in the course.
If you do cheat, we will enforce the UCSD Policy on Integrity of Scholarship (see the UCSD Academic Integrity website). This means: You will get an F in the course, and the Dean of your college will put you on probation or suspend you from UCSD.
What counts as cheating? In CSE 100, you can read books, surf the web, talk to your friends and the CSE 100 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. Yes, we do check every program that is turned in. WRITE YOUR OWN CODE.
To ensure you don't have a problem with this: 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.
Also, in CSE 100, you must write your own answers on the closed-book exams. Getting ansswers from someone else, or providing answers to someone else, is cheating.