5 ms·
> There is a well settled practice in computing that you just don't plagiarize code. Even a small snippet. I think way many developers use StackOverflow sugges
by bfLives 1y ago
> There is a well settled practice in computing that you just don't plagiarize code. Even a small snippet.
I think way many developers use StackOverflow suggests otherwise.
- kazinator 1y agoIn the first place, in order to post to StackOverflow, you are required to have the copyright over the code, and be able to grant them a perpetual license. They redistribute the material under the CC BY-SA 4.0 license. https://creativecommons.org/licenses/by-sa/4.0/ https://creativecommons.org/licenses/by-sa/4.0/ This allows visitors to use the material, with attribution. One can, of course, use the ideas in a SO answer to develop one's own solution.
- behringer 1y agoShow me the professional code base with the attribution to stack overflow and I'll eat my hat.
- _flux 1y agoObviously I cannot show the code base, but when I pick a pre-existing solution from Stackoverflow or elsewhere—though it is quite rare—I do add a comment linking to the source: after all, in case of SA the discussion there might be interesting for the future maintainers of the function. I just checked, though, and the code base I'm now working with has eight stackoverflow links. Not all are even written by me, according to quick check with git blame and git log -S..
- graemep 1y agoI always do to, for exactly the same reason.
- School-Cotton 1y agohttps://github.com/search?q=repo%3AMaterializeInc%2Fmaterialize%20stackoverflow&type=code https://github.com/search?q=repo%3AMaterializeInc%2Fmaterial...
- graemep 1y ago> you are required to have the copyright over the code, and be able to grant them a perpetual license. Which Stack Overflow cannot verify. It might be pulled from a code base, or generated by AI (I would bet a lot is now).