As one who learned programming before Google/StackExchange/etc. I would add that these resources should be the second, or even third, option to figuring something out. There's nothing intrinsically bad about searching for answers, but cut'n'paste won't help you truly understand what's happening.
1) Hit the books (RTFM really is a valid answer)
2) Ask for help/guidance
3) Google
That's probably a better path (unless your s**t is broken in production. Then it's whatever is the fastest).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As one who learned programming before Google/StackExchange/etc. I would add that these resources should be the second, or even third, option to figuring something out. There's nothing intrinsically bad about searching for answers, but cut'n'paste won't help you truly understand what's happening.
1) Hit the books (RTFM really is a valid answer)
2) Ask for help/guidance
3) Google
That's probably a better path (unless your s**t is broken in production. Then it's whatever is the fastest).