What came first, the programmer or the code?
What came first, the programmer or the code?
23 comments
-
Yes, because till University, you’re trying to learn something new. And the best way to learn is by doing.
At work, all you’re trying to do is save money (for the corporation). Best way to do that is to reuse, recycle.
-
It's more complex than that.
In the real world we're not all working on the same assignment...even if it feels like it sometimes.
-
-
-
Anyone can copy code. Making the copied code work well in your own codebase, and fixing it when it doesn't, is what requires skill and experience.
-
It's no exaggeration sometimes it takes a dozen different how-to blogs and stack overflows to find an example where somebody has exactly what you need and nothing more. So many people add so much fluff and unusual structures that the thing they're claiming the code does can't even be found.
-
-
It's almost as if we all work better when working together.
-
Apes together, strong.
-
-
corporates: "what plagiarism?"
-
Talk to the lawyers
-
-
When I get helper functions from stack overflow or similar, I normally add a comment with a link to the article, mostly for my own sake so if there's any problems later I can re-read the article to get more info, or use it to try and find other solutions.
-
Unless there's a bug. Then it is my code and I have to fix it. Immediately. No, I don't want to discuss my thought process for "why I made that decision" I want to fix it. Why are we having a chat about milk pouring technique while it is dripping off the fucking table. Prod is burning and you want to fiddle! (Meanwhile this is a minor bug that nobody has ever actually complained about but just the knowledge that it was my fault...)
-
well using someone's code properly licensed isn't plagiarism
a fair few of my uni classes were like take this guys code and make it do this, which were like 4 lines changes
-
Public domain? Creative commons? MIT? BSD? GPL? You mean I'm allowed to use these things without failing?
-
I have a suspicion that the reason universities crack down on plagiarism this hard (to the point of outright making up offenses like ‘self plagiarism’), is that it’s the only form scientific misconduct that is easy to prove and investigate.
If you are wondering if it’s true, just look at how long it took for Hendrik Schon to get caught. And even then, the smoking gun was reusing (fake) graphs in a publication.
-
They crack down on plagerism because they're trying to teach and assess you, not whoever you copied from. If they wanted copied answers, they could just photocopy the answers for you and save everyone a lot of effort.
The real world may be different, but the idea is to get the knowledge and, more importantly, the way of thinking about your particular subject, into your head. Once you know that, you know what to copy.
-
I was trying to make a larger point about the concept of plagiarism as a form of scientific misconduct. In a teaching setting you are just perpetrating exam fraud and should get nailed to the wall.
-
-
-
-
OUR code
-
Man, I stole your meme
-
-
It's called importing not plageriusm
-
It is called a programming language. I guess repeating some sentences or even the idea for a story is normal when you write a book or code a program.
-
There are also a lot of recurring problems, obscure bugs, performance enhancements that someone has already solved. Software development should care about completing a task, not inventing the wheel (or an image upload) the millionth time.
-
-
It's often the lawyer and the corp who care about suing than the programmers
-
I use dark mode for a reason. FU.
23 comments