If it's a joke "Ahah", if not it's just depressing. SO is a valuable resource to confront and understand concepts. Let's not encourage this copy/paste culture
If we encourage the DRY paradigm in the whole development cycle, copy/pasting a function is just a further reach of such paradigm. Now, if a programmer decides whether or not study and understand the pasted code has nothing to do with the quality of the final product.
Furthermore, IDEs by design encourage copy/pasting to speed development, most offer functionality to store code snippets. In that sense SO is like a web extension of IDEs.
I deeply disagree with this and for such obvious reasons.
It may be a hammer when you're looking for a screwdriver.
Even if you find yourself copy and pasting your -own- written code, you should question why you're having to do that.
Is what you're doing perhaps better abstracted to somewhere else? Be that in an abstract class, a helper class, or even in a separate library from which you can reuse it.
IDEs excel in understanding your code, which helps finding where you've stored something and allows auto-completing access to it, which is almost definitely their most important strength.
No, it's the opposite. The whole point of DRY is you don't copy/paste, you put the thing in a common place and have references to it.
Many SO answers are good enough to be libraries. But they should be libraries, not snippets that are copied and pasted. Fortunately we're moving in that direction - our library infrastructure is becoming good enough that it's worth releasing even small pieces of code as reusable libraries, and people are.
But even if there's copying going on at the implementation level, it's an important conceptual distinction to make.
Its amazing how many people cant.
Being able to search and separate the wheat from the chaff is most definitely a skill. Unless you always want to be reinventing wheels.
EDIT: Unless your job is to invent a better bread recipe.