In my experience, the more context you immediately provide, the less there is a chance of an answer.
You gotta "hook" them with a simple question and then provide context. It's easier to get someone to help after they started, than to have them read 3 pages of context and give you an answer.
Right, which is tip 5 "Get to the point". If you're asking somebody for help, don't trick them or "hook" them. Actually the example you provided has context ("I'm trying to do xyz" and there is code). It shows code, errors and also what you've tried. And it's to the point. So it ticks all five boxes.
Providing context does not mean that you need to describe anything and everything that might ever be relevant. You need to provide enough information for somebody helping you to be able to actually help you.
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.
The best way to get answers is to just write:
I'm trying to do xyz:
But I get this error:
In my experience, the more context you immediately provide, the less there is a chance of an answer.
You gotta "hook" them with a simple question and then provide context. It's easier to get someone to help after they started, than to have them read 3 pages of context and give you an answer.
Right, which is tip 5 "Get to the point". If you're asking somebody for help, don't trick them or "hook" them. Actually the example you provided has context ("I'm trying to do xyz" and there is code). It shows code, errors and also what you've tried. And it's to the point. So it ticks all five boxes.
Providing context does not mean that you need to describe anything and everything that might ever be relevant. You need to provide enough information for somebody helping you to be able to actually help you.