The thing people get wrong: it's important to be able to say very specifically which piece you're not understanding, or what part of your code is breaking.
Bad:
"What's this method for?" (uhhh, did you read it?)
"My code's not working." (uhhh, what have you tried?)
Good:
"I see we have this method and this method, but as far as I can see they're doing the same thing. What's the difference between the two?"
"Can you help me with this? On this line I call this, and I expect the output to be x, but as you can see when I log it here I get y instead."
Here's THE long-standing article that addresses this in depth - in a way that applies to tech generally (beyond dev). Parts seem archaic. It's a Wiki, so overly wordy, etc. But still pretty great overall: catb.org/esr/faqs/smart-questions....
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.
How to ask for help.
The thing people get wrong: it's important to be able to say very specifically which piece you're not understanding, or what part of your code is breaking.
Bad:
Good:
Here's THE long-standing article that addresses this in depth - in a way that applies to tech generally (beyond dev). Parts seem archaic. It's a Wiki, so overly wordy, etc. But still pretty great overall:
catb.org/esr/faqs/smart-questions....