this post was submitted on 06 Feb 2024
1111 points (98.1% liked)
Greentext
4413 readers
2092 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.
Never said they didn't know it wasn't allowed. I said that the teachers view of cheating is flawed. I'm also not saying the students aren't*** (autocorrect likes to change my contractions to the exact opposite) guiltless. My point was that young people make mistakes, and teacher should use this as a teachable moment about the difference between cheating and collaborating. Between just copying code, and knowing how what you copied works. These are students they are still learning. Also, an over 20% fail rate is abysmal and speaks to how poor of a teacher this professor is.
You’re assuming good faith and willingness to learn/change in the part of the students. I was a TA at a private US uni for the not so smart kids of rich parents. Our approach (imposed by admin) was all carrots all the time. 20% seems fair, even low, for the share of students who were there to get a degree with the least amount of effort necessary and then get a job thanks to the uni’s name and their connections.