|
|
|
|
|
by zrobotics
3009 days ago
|
|
I think that there is a solution that is being overlooked, which worked pretty well in my intro class. The professor explained that he would be using plagarism software and wouldn't be accepting excuses. He also explained that he expected to see comments explaining nearly everything, and provided a style guide. While this is training a bad coding practice (who want's to read code that has that many unnecessary comments?), I don't see any way around it for an intro course, since it's really hard to avoid reusing assignments. There aren't that many ways to code 'hello world', but if you make it clear that code must be thoroughly commented then it will drastically reduce false positives. Doesn't stop people copying wholesale from stackexchange, but w/ that level of commenting required I don't think students are really learning less. And this isn't required for higher-level courses, since by that point the assignments are complex enough that accidental plagiarism is extremely unlikely. |
|