this post was submitted on 06 Feb 2024
1112 points (98.1% liked)
Greentext
4600 readers
1997 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
As a software developer I'm expected to, at the very least, to do two things when "plagiarizing":
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.