6 ms·
The worst XY problem is knowing you want to do Y, even if its strange or whatever, asking how to do it, and people asking you "why do Y? Do X instead". Happens
by coldtea 6y ago
The worst XY problem is knowing you want to do Y, even if its strange or whatever, asking how to do it, and people asking you "why do Y? Do X instead".
Happens all the time in Stack Overflow.
Just answer the fucking question, and then give the lecture on why you think it should be done that way, or why it shouldn't be done at all...
- AnIdiotOnTheNet 6y agoYeah, that drives me nuts. It would take me quite a long time to explain the combination of constraints, requirements, goals, and office politics that make Y the thing I actually have to do, yet even when I say as much in the question people still insist that they know my problem domain better than I do. It is maddening. Don't take the actual problem and pretend it is an easier one you know how to solve just to look smart and/or helpful.
- edoceo 6y agoisn't the XY problem that you don't really know you want to do Y? and if you did know, wouldn't you know?
- rzzzt 6y agoYou know you want to do Y, but you don't tell others that you actually want to do X, and Y seems like a reasonable thing (to you) to do to reach X.
- Groxx 6y agoIn the absence of evidence-you-know-you-need-Y: the odds are often HEAVILY skewed towards you not knowing about X, or being confused about either X or Y's purpose. If you do tech support of any kind with random people, it's pretty clear that a majority simply don't know what's available, or why Y may not be a good idea. They need to do a thing, heard that Y can do it, and now they're asking how to use Y - reasonable, but frequently misguided. When Y is dramatically more complex (either harder to set up, or more error-prone to use), recommending X before sinking a ton of effort into explaining Y solves a lot of cases quickly, for both parties.
- xscott 6y agoI once asked a question about an obscure corner of C++. I was only trying to learn more about the language[0]... The answer with the most useful information also contained a long and patronizing rant about why I should never do that. I'm not a novice, and I'm capable of deciding for myself whether I should or shouldn't use something. I just couldn't bring myself to give that jerk credit, so I deleted the question and never logged in again. There are a lot of smart people there, but it's just not worth dealing with them. Maybe this isn't an XY problem, but I suspect it's just as common (at least on most of the Stack Exchange sites). [0] Anyone who thinks they know all of C++ doesn't even know what they don't know.
- js8 6y agoYou have to consider that SO exists not only to answer your specific problem, but also to help other users who might face a similar problem. In that context, it might be helpful to mention, if you are the asking person, include the details why you cannot do X, if you know you can't; or, if your question doesn't include details about your specific circumstance, answers that mention that common solution is to do X instead.
- systemvoltage 6y agoNo. User asks I want to do Y. The responding party should in my opinion: - Provide a solution to Y first. This is OP's point. - Then as a corollary, provide some of their guesswork of what X might be and if it is true, then this is how to solve X without having to do Y. So, it is still beneficial to n00bs and the uninformed, just puts the direct answer to Y first. That's all OP is asking and I agree with that. Most of the time, smartass responses go into the guesswork regime by assuming the User wanted to do X. More than often User actually wanted to do Z, it's not always true and it is polluting SO against the spirit of "Direct question ---> Direct answer" because discovery and searching of answers happen through Y, not X. Most people came to SO because of Y, that's how they landed there in the first place.
- chowells 6y agoThis is not a good approach. For the typical person asking a question, you waste their time at best. At worst, they actually use your solution to Y and ignore why it's bad. Both of those are significantly worse than clarifying the problem in the first place.
- systemvoltage 6y agoNo one is saying we shouldn't provide why Y is bad. I said, it should be a corollary. The bad approach is when the entire thread is full of guesses of what X might be without knowing the full context. Y is nowhere to be found. It breaks the UX of SO.
- moralestapia 6y ago
- chowells 6y agoThere are a few people who frequently have this complaint, but I don't think it's a real problem. If you actually need to do Y in a situation where most people who think they need to do Y are wrong, it's not everyone else's responsibility to divine that you are the magical case. It's your responsibility to demonstrate that you actually do know what you're doing. This isn't something you do by discussing how unfair other people are. It's something you do by communicating the constraints you're working inside, your knowledge of more typical solutions, and why they don't work for you. If you aren't providing that information, you're wasting the time of everyone who is voluntarily helping others. It's not their fault that you're not providing critical information for answering your question effectively. When you're the special case, you have to communicate that fact. It's just wasting everyone's time when you expect others to know it without communication.
- jbay808 6y agoIf you're the one asking the question for the first time, yes, you should make it clear in your wording that you know about X and you really want Y. There are two failure modes though: 1) You really want to do Y, not X. You are not asking the question, just searching for the answer, and find that "how do you do Y?" question, and the answer is "do X instead". Because you're a special case, these answers will likely dominate your search results. 2) You decide to ask the question. You make it very clear that you want to do Y, not X. Your question is closed as a duplicate of the one whose answer was "do X".
- LanceH 6y agoI've come across this multiple times. Some communities are worse than others on StackOverflow about it. Golang in particular seems to look for reasons not to answer a question, and I've come across your 2nd more than once. Typical situation: I get called in as a consultant/freelance/whatever, I inherited X. I can make a small patch if I can do Y. Even when I preface it with "I would normally rewrite X correctly, but that touches on all systems, how can I do Y?" It turns straight into an argument about doing X right. It's like I'm driving, make a left turn and end up lost. They are telling me to make the right turn at Albuquerque instead of the left. Other scenario is that I'm trying to glean some insight on the language and I'll reduce a problem to bare basics and ask something like, "what's going on here?" They will answer "don't use that, use X library instead." That wasn't the question, the question was what's going on with the programming language -- why is it acting weird. I know that nobody would write the code that way, I isolated the problem to specifically inspect a single element.
- etaioinshrdlu 6y agoI suspect the type of person who answers questions unhelpfully like this is often highly experienced, but without terribly deep technical knowledge (in the rigorous, scientific or academic sense). You get an often practical answer, but it's just not helpful when you are pushing the boundaries in any particular domain.
- systemvoltage 6y agoI think people are treating this is as a binary issue. IMO both Y should be answered as well as X should be discussed. Why can't an answer have both? The frustrating part is when Y is never to be found on the answer thread. + 1 on your username :)
- moralestapia 6y agoRegarding SO, it suffers from a strange form of cognitive dissonance: A. You can't ask "what's the best way to do X" because, for whatever reason, these kind of questions are not aligned with "the site's scope". but B. When you ask something specific, you get a lot of "it's better if you do X" answers. I even have had some really nice questions closed because some mods thought I was "asking the wrong thing". Both behaviors are allowed and encouraged ¯\_(ツ)_/¯.
- anigbrowl 6y agoI have also been perplexed by that. I think it's a kind of gatekeeping similar to notability policing on Wikipedia.
- ziml77 6y agoI wonder... What if you made a slight phrasing adjustment to ask "what is the idiomatic way to do X?" Would SO be fine with that? It sounds less like a question inviting opinions even if in many cases the answers will be exactly the same as using the word "best".
- lhorie 6y agoI get these types of questions from time to time, and the way it usually goes is: them: how can I do Y? me: you can do A, but you're probably going to run into B, I'd recommend doing C instead because D them: ok, well, I'm already too committed to Y, so I'm going w/ A. Thanks! them, later: hey, I ran into B. Can you help me? me: ... At that point, I just accept that sometimes people need to get burned to learn their lesson. There are also cases where people ask how to do Y, but explain that it's not an XY problem because such and such reasons. These often actually turn into stimulating conversations because now you're in brainstorming territory and it's clear that the conversation is about procuring novel solutions.
- sleepydog 6y agoI think this is due in part to the gamification in stack overflow. Often Y is a very detailed question that few people know the answer to. But X is a more general problem that anyone knows some answer to. So you answer the question you know how to answer, even if it wasn't asked. However, at least in the case of stackoverflow, you're getting advice for free, even if it's occasionally unhelpful. You aren't entitled to an answer.
- nullc 6y ago> Just answer the fucking question, Beep Boop. Insufficient funds. Insert card to continue. Or perhaps treat other people like humans instead of an answer vending machine? If you came to learn something you failed if you respond like that to someone trying to help. Hope it was worth it.
- pbourke 6y agoI interpret this to mean: if you are going to answer the question, just answer the one asked rather than assuming that the question was asked in error and answering some other one. I don’t interpret this to mean: I’m entitled to your answer. That being said, I appreciate answers of the form: “here’s how you do Y. If you really just wanted X, you can do this instead”
- funyunpowder 6y agoon stack overflow, the more friendly and 'treat other people like humans' esque a question is, the more off track it becomes. dry, cold questions tend to get the best answers. if the goal is to learn something, it's best to treat the site like an answer vending machine. for example, a question treating other people like humans: "hi. I need to get the last two letters of a string in Javascript. can anyone help? thanks" is likely to attract a bunch of curious types of 'why do you need to get the last two letters of a string?' type answers, versus posting something deliberately robotic seeming: "javascript: get last 2 letters of string" immediately gets replied with no-nonsense answers from people wanting to drop their knowledge and get stack overflow green checkmark points for being the fastest answerer etc.
- anonytrary 6y agoTrue! Some XY problems are YY problems in disguise.