Well, when a student doesn't understand his own work, that's a dead giveaway. >This is why a large proportion of a degree should be based on in-class work wher

Well, when a student doesn't understand his own work, that's a dead giveaway. >This is why a large proportion of a degree should be based on in-class work where the student is physically present. I disagree. That's good for a test or two. I have a horribly executed course this semester where all the work is done in class. It's on Android and all the requirements are given at the start of the class. It basically encourages copying from Stack Overflow because you don't have time to learn the API. It advantages people who are familiar with Android because those who aren't don't have time to make up for it by learning. The only thing you can do is learn some specifics beforehand and hope that it will be what the tasks will require. Speed programming is bad programming. Like the saying goes, if the code I wrote so far was a horse, I'd shoot it in the head.