This is a problem.
Those of us here with programming backgrounds have probably had experiences where we sought help in forums,
IRC channels, or even our very own StackOverflow where we clearly stated our abstract problem in concise terms.
Only to be yelled at, downvoted, or just treated rudely by people who want to ask "why" instead of answer "how".
OK sometimes that's necessary but it can also be done in a polite friendly manner.
So some of us, and I am guilty, have gotten into the habit of providing back story to prevent this.
I think another factor is the refrain on StackExchange "What is the problem you are actually facing?"
If you answer that potential retort while posing your initial question you risk making bloated questions and, worse, making them too localized if you're not careful.
But if you leave it out, you risk people assuming your problem is not real and is based on misunderstandings, etc.
And then of course we have plenty of "good" answers which talk about something in the OP's topic, but don't actually attempt to provide an actual answer to their question.
It's a balancing act.
Askers should try to cut out all the chaff but include just enough background to prevent comments and answers that assume they know nothing.
Answerers should assume good faith and address the OP's actual question, and if you think the asker did miss something basic, post a polite comment rather than an answer.
Mods and users with experience should keep an eye out for poorly thought out or poorly worded question, and rude or off topic comments and answers, and boldly edit posts where they can spot and fix the problem, or guide the participants in the ways to make their own questions and answers better.