Comment by al_borland
1 day ago
I wouldn’t worry about students. They won’t be hurting you, only themselves. If the goal is to learn, they aren’t learning. This will either mean programming is a random class they’re taking, not their career, so who cares… or they’ll have a really hard time later in life when they will need to sink or swim in a real job, having not first developed the skills. That’s not a problem for you.
It’s also much more likely they will go to AI these days; the odds of them searching and landing on your repo to use are almost 0. If they do, I imagine most schools would scan for direct copies of existing code.
It's considered my responsibility to protect my labwork at my school, and I could get in trouble if someone else plagiarized it from GitHub.
If that’s the school policy, then there is no fear to get over. Keep the repos private to comply with policy. That makes it easy.
Your school lab work is only valuable to yourself and other students who wish to plagiarize, there's not really a compelling reason to share that code.
If you're writing other software beyond classwork that you wish to share, the school has no say over it, no more than they would if you chose to write a book while in school.
This incentivizes me to minimum effort school projects so I can focus on personal projects.
But most professors want students to be creative and inventive on classwork.
I get that this isn't a problem if I treat my schoolwork as having no utility beyond the course I made it for, but that isn't the ideal.
2 replies →