CSE333 12au (overview)
All of our assignments assume you will be programming within a CSE Linux environment. There are three ways to do this:
We expect 0s and 3s to be relatively rare.
(Many of these policies are taken verbatim from other CSE courses.)
Late Policy: For assignments, there is a 10% penalty for each late day, or portion thereof, up to a maximum of two days late. You will receive a zero for the assignment if it is turned in more than 48 hours late. Also, you get two free late days - two days of lateness with no penalty - to use at your discretion.
For exercises, we will not accept any that are late; you must turn them in on time.
Reasonableness: No set of rules can apply perfectly in every setting. We will make reasonable exceptions, and in return, we expect you to be reasonable as well.
Cheating vs. Collaboration: Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense and is vigorously prosecuted. Vigorous prosecution requires that you be advised of the cheating policy of the course before the offending act.
For this course, the policy is simple: don't cheat. You know it when you're doing it. We'll recognize it when you do it. As an easy example, sharing assignment solution code with each other is cheating. As another easy example, relying heavily on some resource (e.g., some example code you found on the Web) without attributing it in your turnin is cheating.
That said, collaborating is, for many people, an effective way to learn. Learning isn't cheating. Helping each other write programs that are not assignments or exercises isn't cheating. Misrepresenting that you've learned something, or done the work that implies you've learned something, almost certainly is.