this post was submitted on 06 Feb 2024
1110 points (98.1% liked)
Greentext
4430 readers
908 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I understand cheating is shitty but it would make a lot more sense for the teacher to make this a teachable moment about cheating, and to promote collaborative solutions, but also checking work you get from others.
A huge part of development is copying code and reusing code from libraries. The important part is that you know how the code you copy works.
If you give cheaters too many chances, the other students will feel betrayed. And I guess rightly so.
It's not uncommon to get mails directly, or later in course evaluation, from students who complain about other students that didn't put in the work. I can only remember few cases where there were names involved. Typically it's some general complaint, but the frustration is obvious.
It sucks when you make an effort but witness other students cheating their way through the class. What are we supposed to tell them when the dishonest behaviour of other students doesn't cause any consequences?
You tell them that they have learned the important life lesson:
In most situations, results matter more than the means by which you got them.
I actually see it as a good opportunity to teach them that means matter. By kicking cheaters out of the course.