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.
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.
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.
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
It’s called importing not plageriusm
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…)
Public domain? Creative commons? MIT? BSD? GPL? You mean I’m allowed to use these things without failing?
I use dark mode for a reason. FU.
