> We had a particularly articulate young man in our graduating class that argued that checking the book is ultimately not cheating in the world of professional

> We had a particularly articulate young man in our graduating class that argued that checking the book is ultimately not cheating in the world of professional CS and software development. My school's CS department defaulted to allowing students to use almost any available resource (unless specifically indicated otherwise). But you were required to write down what resources you used. So a professor might assign a whole pile of nasty algorithm proofs, and say, "You're allowed to work in groups to find the general solution. But you need to write down your group members, and you need to do your own writeups." Tests were in person but not especially proctored. The penalty for cheating was a heavy suspension and a transcript annotation, with permanent expulsion for a second offense. This actually worked pretty well, back in the day.