10 ms·
There's some nice examples of something I've noticed - where you have a very clear issue and people pick away at stuff that's orthogonal to the issue and won't
by smcl 5y ago
There's some nice examples of something I've noticed - where you have a very clear issue and people pick away at stuff that's orthogonal to the issue and won't resolve anything. The question is clear, "gimme gimme gimme" is printed to stderr, it's not expected and we'd like to know why ... but there's comments like:
- "Why does your test script call man where it should fail?"
- "why do you need to do a 'man -w' every minutes?"
I get that there's a bit of mistrust in some things users report so in some cases we as developers need to be careful to establish the user's actual intent or whether they're describing their issue correctly. But this isn't one of those cases.
- matsemann 5y agoI get why people ask questions like that. Many questions on SO are often weird because of the XY problem [0]. Someone asks for X, people answering think doing X is really weird and difficult, and thus dig a bit more. They then find that the asker really wants to achieve Y which is simple to do. [0]: https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem https://meta.stackexchange.com/questions/66377/what-is-the-x...
- skohan 5y agoI find this frustrating because I often want exactly
- matsemann 5y agoYeah, I get that as well and sometimes feel the same. The difference is that a beginner tries to do Y, fails, think they can solve it by doing subtask X, so they ask X. But us with more experience know why Y didn't work and probably have a good reason for asking X. But the answerers cannot know that. So adding a small snippet of what have been tried, or why X specific is what's needed is a good idea to steer the conversation in the correct direction.
- AnIdiotOnTheNet 5y agoIn my experience, if you tell people your use case for wanting to do X instead of Y, they'll just attack your use case instead. I, for one, never use places like SO anymore because everyone just wants to pretend you really want Y, because that's an answer they know.
- dkarl 5y agoI use SO all the time for gleaning information from the answers, but never for asking questions, for this very reason. The questions that show up in search results are full of great answers and information, but mine ended up full of people who didn't know the answer to my question but were eager to tell me about something they did know. Then I'd put more and more effort into providing context and justifying the question, until eventually the answers dried up. I decided I was better off seeking help on mailing lists, issue trackers, chat rooms, etc.
- skohan 5y agoYeah honestly I feel like it has gotten a lot worse since I was using it actively maybe 8-10 years ago. It seems to have moved towards a lot of people playing the karma game, and trying to focus on every flaw rather than trying to answer the question and give help. Nowadays, I usually try to find a community or forum directly related to the specific subject I'm working on. However, it's hard to tell if the quality has actually changed, or whether it's just more geared towards novice programmers and I'm just not asking the type of questions that get help on the platform anymore.
- praptak 5y agoThen specify the context as part of your question: "I want X. I think alternative solutions like Y won't work because...". As it is with many things in life the more effort you invest in the question, the greater the returns :) Although tbh I quite often want the opposite, so I add "Alternative solutions/workarounds welcome" or "I don't see how I can avoid doing X but maybe..."
- pessimizer 5y ago> "I want X. I think alternative solutions like Y won't work because..." Listing all of the things you don't want to do would not only take up more words and effort than the question about what you do want to do, but is hopeless. Somebody who doesn't know the answer to your question but still wants to comment will find something that you were unaware you didn't want to do. It's better just to answer questions directly, and then when somebody uses that solution and it doesn't get them closer to the solution to their real problem, they'll ask a better question.
- mixedCase 5y agoSorry, but that doesn't make sense and sounds like a rationalization for being lazy with the question. You're worrying about a straw man instead of trying to help out people who do know how to deal with the actual problem you have. And bad solutions can still "solve" problems with horrible trade-offs, so instead of searching again for a better solution people may just employ the worse one unaware of the better possibilities, consequences be damned.
- skohan 5y agoI think it depends on the quality of the question. For instance, if it's a semi-vague question just pointing in the direction of a solution, then I think it's fair to question the motivation of the poster. But if it's a very precise question about how to accomplish something specific, I think the burden should be on the person answering to add the clause: "you can do X, but its generally not considered a good idea because Y". Honestly if you can't answer the original question, I get the impression you're just trying to be a smarty-pants and show off some domain knowledge you have which is related to the task at hand.
- latexr 5y agoThe XY problem applies when someone asks how to accomplish something. In this case they want to know why something happens; what they’re doing around it is irrelevant. It’s analogous to asking “why does pizza taste metallic to me?” and getting “why are you eating pizza?” as a reply.
- matsemann 5y agoNo, the pizza analogy doesn't work. It's the specific use of man here being questioned ("why is it used in a test?"), not man usage in general.
- johnbcoughlin 5y agoWhy does pizza taste metallic to me when I eat it on a boat?
- deleted 5y ago[deleted]
- latexr 5y agoAnalogies don’t have to be one-to-one. It’s close—and simple—enough to get the larger point across.
- matsemann 5y agoIt doesn't, though. As I see why asking "why are you eating pizza is wrong", but not why asking "why are you using man in your tests" is wrong. So your analogy is more of a misrepresentation of the situation than anything else. If you don't want focus on the details, then don't provide them. If you provide them, it has to be because you think they might be relevant. And then it's relevant for people to ask for further details.
- xboxnolifes 5y agoIt's analogous because the existence of tests have absolutely nothing to do with the question at all.
- don-code 5y agoI've been learning to recognize when I've been presented with a solution, rather than a need. Often times the solution answers the need, but lacks knowledge of either side effects, implementation time needed, holes in leaky abstractions, or something else that makes it less than ideal. Walking back to the need helps in proposing a better solution.
- tarsinge 5y agoI personally hate when that happens because usually I really want to do X for good reasons. In the end the people asking got help on troubleshooting their specific problem, but the question is still unanswered (or answered by “You don’t want to do that because you’re a beginner”).
- patrickthebold 5y agoI'm the opposite. I often catch myself asking about Y and then needing to back up and ask about X. I even know the problem by name and can't help (occasionally) asking the wrong question.
- tarsinge 5y agoI don't disagree, but then the question should be phrased that way, or it should be mentioned than there may be better way for generic use cases but the original question still answered.
- shawnz 5y agoIf you are so unfamiliar with X that you require the advice of experts to implement it, then how can you say so confidently that the reasons to do X instead of Y are justified, even though those experts disagree? If it's really true that the conventional wisdom about Y is just wrong, and X really is better in some cases, then it will be a long process to get all the experts to reconsider their assumptions, requiring battle-tested proof, and that probably won't happen in a single SO thread.
- tarsinge 5y agoI'm not unfamiliar with the problem space and why I want to do X, I'm just looking on implementation details. If the question was "How should I solve that problem? Should I use X?", then sure "use Y instead because it's a better practice" would be a valid answer.
- kosievdmerwe 5y agoReminds me of the time I asked "How can I do this Python feature in one-line because I'm writing a to-one-line Python transformer". Still got idiots replying that I shouldn't be doing what I want to do in one line.
- CoolGuySteve 5y agoThat may be true but it often ruins StackOverflow as a repository of answers. There’s nothing worse than actually needing to do X only to find a StackOverflow page where 10 different answers give 10 different Ys. Or when X needs to be done but instead all the comments hector the question with useless criticism.
- shawnz 5y agoIf a subject matter expert thinks that people asking for X are falling victim to the XY problem, then I want to hear about it before I go down the mistaken road of implementing X. If there truly is a circumstance which makes X the right solution, then that might warrant a new question being posted with the additional context to make that so. But I suspect it's much more often the case that the asker is simply being stubborn and doesn't want to change their plans.
- CoolGuySteve 5y agoBut the new question almost always gets closed as a dupe in spite of clarification.
- shawnz 5y agoYes, I could agree with you there. I'm not going to defend the stickler moderators on there (just look how they shut down the interesting comments on the top answer).
- cperciva 5y agoYou seem to be under the impression that people answering questions on SO are subject matter experts.
- robinson7d 5y agoYou’re correct that they often aren’t, but all the same I find it amusing to read this comment attached to a StackOverflow link where the exact person who suggested “gimme gimme gimme” and the implementer both answered. Obviously not the ones making the “why are you $X” comments in this case though.
- bjowen 5y agoThis is also why the canonical answer of turning it off and on again is a meme.
- staticassertion 5y agoThe people who answer Y without addressing X are far more annoying and detrimental than the people asking X. If you see a likely XY problem, answer X, then explain why they might want Y, and then answer Y.
- whatshisface 5y agoThe XY problem in theory: An expert with broader knowledge than you realizes what you really should be asking. The XY problem in practice: Someone doesn't know the answer to your question so they randomly choose a response from the ten things they do know. Also: If we're calling it the "XY problem," does that make it mansplaining? (XY? Get it? Sorry.)
- shawnz 5y agoIf someone only has a tangential knowledge of the problem, would it be better if they just don't give their input at all and simply leave the thread empty? Non-experts contributing their opinion doesn't take away space from the experts to answer it properly. If the advice is really that bad or uninformed, then it should just be downvoted. That's not really related to the "XY problem".
- whatshisface 5y agoOn stack overflow, having several tangential non-answers will make the question look well-answered, potentially misdirecting the real expert away from it by creating a false impression.
- deleted 5y ago[deleted]
- kasabali 5y ago> Non-experts contributing their opinion doesn't take away space from the experts to answer it properly. Ever heard of a thing called signal to noise ratio?
- xienze 5y ago> people pick away at stuff that's orthogonal to the issue and won't resolve anything. Sometimes it’s a case of “I don’t know the answer to that, but I’d like to help. I’d like to know more about why you’re doing that so I can perhaps suggest something that doesn’t require doing that anymore.” Which indeed may be very helpful because even if you knew the real answer to your problem, in many cases you’ll need a workaround since the behavior probably won’t be fixed anytime soon.
- Ballas 5y agoWell, in this case I would also like to know, out of pure curiosity. I cannot come up with a viable reason on my own why you would run 'man -w' as part of a test.
- loopz 5y agoWhy would you even ask such a question to begin with? You say curiosity, but there seems to be more to it?
- fendy3002 5y agoAsking why to a part of code or workflow is a good thing, even only because of curiosity. After knowing it, you may find the reasoning brilliant, or ridiculous and dismiss it and that's it. However if any chance you have the same situation as OP, it may come out valuable, either currently or in the future.
- klyrs 5y agoI would have asked the same question for the same reason. A sibling comment introduced me to a feature that I wasn't familiar with. And that's why I'll continue asking curious questions until the day I die.
- gpvos 5y agoWhy would there be more to it? I wanted to ask the same question, just because I simply did not know the answer. In fact, I am curious how you became so wary about such a simple, uncomplicated and direct question.
- loopz 5y agoIt was meant as joke, question the questioneer, for an honorary -4.
- jmiserez 5y agoVerifying you have your environment and search paths setup correctly. From the man page: > -w, --where, --path, --location Don't actually display the manual page, but do print the location of the source nroff file that would be formatted.
- jl6 5y agoI think it’s similar to how experienced users access consumer support processes. When you call a support line, you might know exactly what you want, and just want to be routed to the process you know you need, but 95% of customers are better served by being put through the “have you tried turning it off and on again” process. Similarly on Stackoverflow, a majority of users probably are doing it wrong and are helped by the XY-troubleshooting approach. Experienced users who really do want X end up being collateral damage.
- jamincan 5y agoSometimes experienced users are also served well by walking through the steps. At least at our company, you see field technicians who think they know what is happening and try to short-circuit the troubleshooting process. Sometimes they are correct, but oftentimes they miss a significant detail that they would have caught if they had just followed the normal procedure.
- latexr 5y agoBefore applying an XY troubleshooting approach, one should learn to recognise XY problems. While some cases may be ambiguous, I’d argue this one isn’t.
- cm2187 5y agoIt can be useful. I remember asking about a problem I ran into in a convoluted solution and someone suggested I should try a much simpler solution which was actually a better idea.
- Semiapies 5y agoIt can be, if the people involved are knowledgeable. In this case and a distressing number of other cases, it's clear the people piping up have no idea what's going on (and some aren't even paying attention when reading the initial question). They're imitating what knowledgeable people do to feel like they're contributing.
- AnIdiotOnTheNet 5y agoPeople prefer problems they know the answer to. Sometimes, when they don't know the answer to a problem, they'll try to cram it into a shape they recognize so the answer they already have works.
- Semiapies 5y agoI think that's much more the case than the whole "XY" issue. It's clear the people asking "clarifying" questions about the workflow didn't have the slightest idea that man did that, much less why. But they can't get points or a feeling of accomplishment from recognizing that they're out of their depth and staying out of the discussion.
- lucideer 5y ago> this isn't one of those cases. Reading all of the replies and context around the solutions, you're right that it doesn't appear to be one of those cases. But I don't think it was that clear cut from the original question. The counter to this is, I believe, much much more common on SO: someone comes up with an odd solution to a problem in their head, tries to implement said solution, runs into challenges and comes to SO asking for help making their solution work. That then leads to over-engineered workarounds for hurdles they would not have encountered had they asked for help with their actual problem.
- btbuildem 5y agoIt's a bit of a Stackoverflow trope, so much so that it shows up in these "parody questions" that surface from time to time. In some cases the people answering have the experience and breadth of knowledge to understand the "real" question being asked, even if the OP doesn't quite have it yet. Other cases, it seems like arrogance and showboating, and doesn't contribute much where a simple direct answer would be best. The one that gets me is seeing an answered question, with a bajillion upvotes, locked by mods as "off topic" or "not useful" or whatever. Clearly a relevant question with a useful answer, as evidenced by the many comments and kudos. Ugh.
- Semiapies 5y agoSee also the questions that amount to "Why aren't you using the operating system/language/framework/library I'm actually familiar with, so I can answer you and get points?"
- at_a_remove 5y agoThat is one of the things that turned me off of Linux in the very early days ... every time I tried to find out how to do something, I was a big moron for not using someone else's distro.
- mmcgaha 5y agoI think it is something like the old joke where you tell the doctor that it hurts when you do something and the doctor says stop doing it. Often, we can eliminate the problem by factoring it out altogether. In this case people observed the problem to be solved as a failing test case. The author could have avoided being ask why by just stating the facts and not trying to explain why he observed it.
- Semiapies 5y agoNo, they'd ask twice as many questions in that case.
- panzagl 5y agoI like to read the reasoning behind things that appear to be spurious because sometimes it turns out they have a good reason for doing it that I haven't considered, and it might be something I want to incorporate in my practices.
- lwerdna 5y agoThanks for articulating this. I call them XY inquisitors. We had a couple at work a few years ago and any question directed at them was met with a somewhat derisive "What are you trying to DO?". Of course there are cases where the question poser of Y benefits from having their X identified, an archetypal case here: https://stackoverflow.com/questions/2691018/decimalformat-and-double-valueof/2691162 https://stackoverflow.com/questions/2691018/decimalformat-an...
- moralestapia 5y agoAnd that's not even an XY example ... You guys are so confused you don't even get yourselves.
- SamBam 5y agoSure it was. But it was a good example, because the person helpfully starts with "I'm trying to do X." But they still say. "I'm trying to do X. To do this, I'm doing this complicated Y. How come Y doesn't work?" This is still XY because they're asking about Y. But in the bad cases, they'd only mention the Y part, and omit that they're trying to do X.
- moralestapia 5y agoThe XY problem is "I'm trying to do Y" -> "Are you sure you don't want X?" This is "I'm trying to do X" -> "Here's how you do X"
- SamBam 5y agoNo, not exactly. From [1], the XY problem is "you are trying to solve problem X, and you think solution Y would work, but instead of asking about X when you run into trouble, you ask about Y." So person is trying to solve X, but asks "How do you do Y?" "Why are you trying to do Y?" "Well, I want X and Y seems to be the solution" "No, to solve X you want to do Z." In this case the asker nicely gave their X as part of the question, but the bulk of the question was still about trying to move forward on their mistaken "solution" Y. 1. https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem https://meta.stackexchange.com/questions/66377/what-is-the-x... (and note all the other answers saying the same thing.)
- noptd 5y agoAgreed. IMO StackOverflow would be greatly improved if they implemented a rule barring these responses unless they first answer the actual question at hand. To build off of another user's example, answering >"If I eat pizza in the morning, why does it taste metallic?" with >"Because of a chemical reaction due to blah blah blah... which raises the question- why are you eating pizza for breakfast anyways? Avocado toast is superior for <reasons>" Would be far more productive of a response for both cohorts of users; those searching for the direct answer and those searching for a better solution of what to have for breakfast.