> Let's agree that copy/paste from stack overflow is bad I think context is important. It's not inherently bad. If you are inexperienced or don't know what t

> Let's agree that copy/paste from stack overflow is bad I think context is important. It's not inherently bad. If you are inexperienced or don't know what the code/command is doing then yes that's not ideal. But competent developers using Stack Overflow (and all other external memory devices) appropriately to aid their workflow is perfectly valid. I rarely copy/paste verbatim from Stack Overflow (apart from perhaps bash commands where the answer is literally the exact command I need - and in that case, why would I not use it?). But I do copy/paste, as long as I understand the code, and then adjust it accordingly. In my experience of coaching junior devs. The number one skill I've had to train them in, above all else, is the ability to efficiently search for and find answers to their questions/unknowns quickly. (As well as digest those answers and incorporate the knowledge into their understanding - not just blind copy/paste). I'd go as far as to say that If you are a developer in 2021 and not constantly looking up things for reference (whether to jog your memory or to quickly learn new concepts) then you're either a genius with a photographic memory, working in a very constrained domain that isn't stretching you or you're just plain doing it wrong. :-)