I find it obnoxious to waste time on an OS from 2013, but asking-to-answer is accepted behavior on stackoverflow: https://stackoverflow.blog/2011/07/01/its-ok-to-ask-and-answ...
If you had a difficult problem, didn't find a solution on stack overflow, but did figure it out before you had a chance to write up a question, put it up (with the answer) anyway. It might be useful to someone else.
This is the key thing that newcomers to Stack Overflow don't realize. Not understanding this distinction between a Q&A forum vs a Q&A archive is why people get so pissed at SO being quick to close off-topic and duplicate questions.
That's not exactly accurate with regards to the current options for voting to close a question. But the general reasoning here is that it's an anti-spam measure. It filters out low-effort questions (eg. homework questions) and forces you to be specific and concrete enough with your question for the question to be suitable for SO.
Simply describing the task and providing sample inputs and outputs tends to be too open-ended and often strays into the territory of asking for someone else to write all the code for you, rather than help you solve a specific problem with your code.
There's a huge difference.
Ideally, yes you're right.