4 ms·
The most amusing variant of the XY problem is when you want a seemingly ridiculous Y, and then, when people inevitably ask why, you tell them about your entirel
by derefr 7y ago
The most amusing variant of the XY problem is when you want a seemingly ridiculous Y, and then, when people inevitably ask why, you tell them about your entirely-novel X, which they still don’t understand the use for, so you have to explain the entirely-novel W that motivates X, and so on... and by the time you’re done, you’ve explained your whole business model, written a ten-page journal paper, and completely killed the conversation—because they don’t feel they have the prerequisite knowledge to talk about A-through-X, so you just get a “good luck with that, buddy.”
Even though Y was a concrete problem that they do have domain experience in solving!
I call this “going up the rabbit hole.”
——
Example (deliberately shortened from its real depth):
• I’m trying to invent a novel algorithm for inter-procedural data-flow analysis, because none of the existing ones work for me.
• Why? Because I’m trying to reverse a stack machine bytecode with only indirect jumps and no reified CALL/RET opcodes, into a structured inter-procedural control-flow-graph.
• Why? Because I want to do program-slicing to recover HLL representations of key-value-store writes that the program does.
• Why? Because I want to use them as hints for my runtime execution tracer for said bytecode, so it can emit better traces.
• Why? Because I want to put those traces into an OLAP database and I want the data in the DB to be typed.
• Why? Because these traces are the only canonical representation of the state of the system, and our business model is allowing auditors to figure out what’s going on with the system.
- 0xffff2 7y agoThis is why on the rare occasion that I find myself answering questions on IRC or Stack Overflow I always start with at least a simple answer to the question asked. Only once I've taken a stab at answering the question do I consider moving on to "but, what are you really doing..." Another related type of question is a question born out of curiosity rather than need. Sometimes you want to do things just for fun to see how they work, but you get shut down every time you ask a question because "you should never do that in production".
- winstonewert 7y agohmm... so I do this in the opposite order... I start with, "hey, you probably shouldn't do this, but assuming for the moment that you really want to for some strange reason..."
- delecti 7y agoI think it's generally good to always do both, on both sides. If you're asking, start with what you want, and then a why. If you're answering, I'm not sure the order is as important, but starting with whichever is shorter is probably a safe general rule.
- deleted 7y ago[deleted]
- anfilt 7y agoI hate when people say you never should that in production. A lot times when I am doing something weird it's for fun.
- dahart 7y ago> I call this “going up the rabbit hole.” Love it, that’s great! Adding it to my lexicon.
- StavrosK 7y agoI hate that, I ask for help with an odd Y and say "I've researched all other solutions and they didn't work, so can someone please help with Y?" but people still make me show them my work and convince them that everything else actually won't work before they maybe help.
- kuroguro 7y agoI've found that if I need something oddly specific most people wouldn't be able to help anyway (and those who could would have to invest a lot of time in that specific case to understand it). I've simply stopped asking for help with those. IMO there's some point after which it's counterproductive for both parties.
- deleted 7y ago[deleted]
- infogulch 7y agoIn my experience this can happen for two distinct reasons (not exclusively): 1. The StackOverflow Reflex, where the person responding doesn't believe you've actually explored other solutions sufficiently because in their experience the vast majority of the time the person asking for help hasn't actually explored other solutions effectively. This may feel like bad faith (from either side), but it could just be the asker's inexperience with other solutions that cause them to not apply them correctly. 2. They don't know how to do Y, but they know how to do X really well so they want to make sure you haven't missed anything in your attempt to make X work. Remember that different people have different expertise and may want to try to help solve your problem even if they don't know how to solve it with your chosen solution. I think askers often don't recognize that explaining why T-X won't work in their case is actually very helpful to fully understand the problem, even if the person helping ends up solving Y directly. If you're asking for help solving a complex problem, sometimes you have to teach the problem to the person helping you. And that's ok.
- StavrosK 7y agoI agree, and there's no simple way to signal that you really do know your stuff and really have investigated other solutions. The one or two times I tried this, responders became slightly hostile after a bit, implying that I didn't know what I was talking about, that I was doing things wrong, that my constraints weren't real, etc. It was probably as frustrating for them as it was for me.
- iovrthoughtthis 7y agoThis is like going: Hi, i need $10. Why? Because I need to buy a beer. Why? Because the man at the bike shop is super thirsty. Why is that important? Because If I sate his thirst he said he’d introduce me to his manager. Why is that important? Because I want to work at the bike store and it’s the only way to get an intro. “The traces are the only canonical representation of the state of the system” Why?
- whatshisface 7y agoWhat's the basis for this extreme skepticism, is it an accepted law that every problem in programing can be solved with some basic plumbing? My guess for why so many people love the X->Y thing is that it allows them to join in on discussions where they have no idea how to answer the question.
- derefr 7y agoI mean, past that point, you've left "technical problem" land and entered "a description of what the business sees as an exploitable market opportunity." But to be pithy, it's because the system is all of: • intentionally brain-damaged for OLAP, by a design focusing on OLTP efficiency to the exclusion of all else (think: bit-packing structs into k-v values in a way opaque to anything other than the program that owns the values; no binary object-wrapper format like ELF to describe which ISA is in use by a bytecode program; etc.) • very popular (enough that auditors are interested) • a competitive mutually-untrustworthy multi-tenant platform, where people have every incentive to obfuscate any sort of event logs their programs emit, so that they can keep the competitive advantage of analyzing those logs to themselves Or, in short: the system is a scrambled egg, and people are willing to pay to have it unscrambled for them. Most developers would just say "you can't unscramble an egg" and give up. But the schema information is there to recover—it's just burned into the logic of bytecode programs. Someone with the right expertise can recover it.
- jfindley 7y agoSure, there are cases where seemingly-ridiculous things are actually needed. Where a lot of people commenting on this article are failing, though is thinking only about their needs and what they want. The people responding to your IRC message/ML post/etc are (usually) giving up their valuable time to help others for free, and making some accommodation for this is essential if you want to get anywhere useful. On top of this, when you join a room/list where you aren't well known, the responders have no context on who you are, your level of experience, etc[0] - but what they DO have is long, long experience with people asking XY questions where Y is both ridiculous and not going to solve X anyway. I know it's frustrating to have to go through your reasons when you are certain that damn_silly_thing_Y is actually the only way of solving your problem, but it is needed. After all, you're asking these people because they're likely more experienced than you are (or else why ask them?) and thus there's a chance you could be wrong. 0: And you can't often shortcut this - due to astronomically high rates of Dunning-Kruger cognitive bias in many of these venues, starting out with "I'm an expert, I know what I'm doing" without very convincing evidence is usually extremely counter-productive.
- derefr 7y agoI think you confused my point for the point of the OP, and then just typed a reply that is basically a reply to the OP. My point was the fact that, at the end of the justification chain, you've generally left the domain of expertise of the expert/forum of experts that you came to. Because of this, the people you're conversing with will fail to actually help you with your problem, because they've been dazed/confused/distracted by the higher-level problem statements that exist outside their domain of expertise. Even though the immediate problem is one they're eminently qualified to solve. It's unintentional nerd-sniping: they force you to tell them about a larger problem that they don't know how to solve—sometimes, in my case, because it's a research problem and nobody knows how to solve it—and they get distracted trying to understand the entire breadth of a topic they may not have ever considered before, in order to figure out how they would solve the highest-level problem themselves. They never "come down to earth" to solve your immediate problem. It's as if you went to a low-ranking soldier and asked something about how well some body-armor they use works in practice, and they asked you what the context is, eventually demanding you to explain the whole strategy of the war to them, at which point they get confused trying to understand the strategy and politics of the war they're fighting, which is usually inevitable because they're a soldier, not a politician.
- catern 7y agoI've just started immediately telling them my high level project if they ask why I am doing something. Even though I really doubt it will aid understanding and fixing my problem, since my high level projects are highly obscure research projects, it at least saves time. And then they'll either go away, or give a solution to my original problem; if they start questioning my research project I can just ignore them, though that has not actually happened yet.
- Waterluvian 7y agoI get this sometimes when I'm trying to learn about a suboptimal solution. I can even preface the question with, "I know this isn't the best solution but can you explain why it works..." Inevitably I get, "you shouldn't do it that way..."
- LanceH 7y agoWelcome to stack overflow.
- deleted 7y ago[deleted]
- floren 7y ago> I call this “going up the rabbit hole.” I just call it "posting on Stack Overflow"
- jonahx 7y agoI call it "the IRC smugness pit". The asker knows that providing the full A-X context would be an utter waste of time, and really does want an answer to Y only. Certain IRC regs will flat out refuse to answer Y. Often this is because they don't know the answer to Y, but instead of saying so would prefer to wear the mantle of wise interrogator of "things you did not think of"™. Ofc, sometimes they're talking to a newb and this is appropriate, but jumping to "this is an XY problem" seems to be a knee-jerk reaction for some people.
- jacobolus 7y agoOne of the more effective albeit mildly dishonest to get around this on IRC is to troll the channel. “I asked my buddy who claims to be a language C expert and he told me that it is completely impossible to accomplish Y using language C, because «invalid reason Q that makes language C sound bad». Then all of the smug jerks who would usually start by asking what kind of idiot would ever want to do Y will instead fall over themselves to prove that Y is possible and really quite simple to accomplish, and explaining that my expert friend who said it was impossible had no idea what he was talking about. Make sure to use a pseudonym for this one though if you want to come back to the channel and not have people still mad at you.