this post was submitted on 06 Feb 2024
1117 points (98.1% liked)

Greentext

4728 readers
2532 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:

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
[–] [email protected] 241 points 11 months ago* (last edited 11 months ago) (90 children)

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.

[–] [email protected] 21 points 11 months ago (1 children)

Keep in mind, it's likely that more people cheated, but the smarter ones changed just enough code to make it look "their own", or actually tested to ensure it'd work, and thus weren't caught. Those 22 caught are very likely the ones that copy-pasted verbatim.

[–] LemmysMum 8 points 11 months ago

Then the smarter ones fulfilled the task, knowing and understanding the material enough to provide a working solution, rather than paste a non-working one. They may have done less than someone working from scratch but they showed themselves no less competent in the material.

load more comments (88 replies)