Their teachable moment is that plagiarism has consequences, and they earned that lesson entirely by themselves.
Sure, but as a general rule the carrot is a better incentive than the stick.
Let’s not pretend these are kids who have a test for their first time. They all were told to not cheat and that cheating would lead to expulsion.
I refuse to feel bad knowing that chances are they have been given an opportunity that many others would never get.
On the flip side, all threat of consequences works as a deterrent only when there’s the expectation to be caught and punished.
By always catching but never handing out punishment to kids violating rules, you only teach them that consequences are inconsequential.
To clarify, I wasn’t trying to argue there shouldn’t be consequences, just that depending on severity it must be proportional.
I want to compare it to the US justice system where, from an outsiders perspective, many are judged unnecessarily harsh. This makes it harder for people to “come back” after release and creates a societal loss.
I’ll end it there because I cba to write more but, eh, just my thoughts. Some nuance is lost in translation too.
As a software developer I’m expected to, at the very least, to do two things when “plagiarizing”:
- Find the source to copy from.
- Perform the necessary adjustments to apply that copied solution to my own problem.
When students plagiarize, they don’t even need to do that. The solution they are copying from was written for the exact same assignment, so they don’t need the adjust anything (at most, they change some identifiers to throw off plagiarism detectors). And they copy from each other, so they don’t need to search for a solution. They may need to apply some social skills to find out who to copy from - but these are vastly different from the technical skills required to find relevant code to “plagiarize” in real world programming.