this post was submitted on 06 Feb 2024
1110 points (98.1% liked)
Greentext
4459 readers
504 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.
i wish my deadlines are not hard enough so that i could actually take time to learn everything from the code i copy.
Don't worry -- you don't have to cope with too-short deadlines after you're dead. Up to that minute, and especially after graduation, though, it's all deadlines and priorities. Grok the concept.
You'll find the head-fake (as Randy Pausch calls it) is teaching you to manage your time and priorities WHILE you're learning your craft. Like how we learned C++ in an algo course by having the Prof teach Zero C++ and expecting us to pick it up.
Sure, committing to a deadline is reasonable if you are included in the decision calculus of scope vs time. Part of that should be to include space for learning as needed to understand anything you'd copy.
Omitting that is a recipe for low quality garbage and not only will the code suffer, but the organization also will while all the staff fall behind any competitors who make the investment.