• Marxism-Fennekinism@lemmy.ml
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    1 year ago

    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.

    • llama@midwest.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      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.

  • BeigeAgenda@lemmy.ca
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 year ago

    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.

  • Rheios@ttrpg.network
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    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…)

  • llama@midwest.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Public domain? Creative commons? MIT? BSD? GPL? You mean I’m allowed to use these things without failing?

  • vzq@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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.

  • Still@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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