My biggest frustration when asking for help is somewhat similar problem where others offer solutions that sound simplier but are more complicated in practice for example
Me: I'm having an issue setting up a feature in kubernetes
Foo: use bash instead it's much simpler and you can solve your problem with one setting
Me: ah ok, let me tell my team of 70 devs we're uninstalling kubernetes and writing our own orchestrator in bash because Foo on IRC says it's simpler
Sometimes everyone acknowledges and wishes that solving X were the path forward, but for political, inertial, technical-debt, financial, or stubborn customer-related reasons, we must think only about Y.
These conversations often end with the responder saying "then you should change teams." Which might be the ultimate XY answer.
If someone without the necessary expertise chimes in with an unhelpful answer within minutes of a question being asked, then everyone who comes after must check their answer before deciding if the user still needs help.
But even worse, I think potential responders on StackOverflow may not read the question at all because it will be listed as already having an answer. It won’t be an accepted answer, sure. But it still disincentivizes attention to the question. (I know it certainly disincentivizes me when I go looking for SO questions to answer.)
If a question has gone unanswered for hours or days, then sure — offer whatever advice you’ve got. But before then, you’re just adding noise, and actually reducing the chances that the OP will get what they were looking for.
Me: I'm having an issue setting up a feature in kubernetes
Foo: use bash instead it's much simpler and you can solve your problem with one setting
Me: ah ok, let me tell my team of 70 devs we're uninstalling kubernetes and writing our own orchestrator in bash because Foo on IRC says it's simpler