4 ms·
I hate when the top answers on stack exchange sites are suggestions to do something completely different (don't write your own web store). I wonder how that cou
by mrspandex 15y ago
I hate when the top answers on stack exchange sites are suggestions to do something completely different (don't write your own web store). I wonder how that could be avoided. Should he have worded the question differently? Should there be separate upvotes for "answers question" and "useful information"?
- MostAwesomeDude 15y agoOn help groups, it has become common to address the XY problem: A user cannot solve problem X, but thinks that problem Y is equivalent and tries to solve that. The user can't solve Y either, and goes to ask for help on problem Y, without mentioning problem X. Of course, this doesn't apply to this particular question, but I figured I'd explain why people do this.
- alttag 15y agoMmmm... I think it's more than that. It's been my experience that questioners don't always ask the right question. For example, consider the (not entirely) hypothetical "How do I implement drop-down menus?" What the person typically needs is some sort of navigable interface for a web site--but that's not what they ask for. How is the root question uncovered? By asking questions. (Why do you need it? How far along is the project?) The best solution answers both what they asked and what they should have asked. The reason people do this (as you say) is that they sometimes have enough experience to suggest a different path altogether.