6 ms·
George: I’m doing X, and I got this error, how do I fix it Jasminda: Are you actually trying to do Y? If so, you shouldn’t do X, you should do Z instead Arg
by jeffbee 6y ago
George: I’m doing X, and I got this error, how do I fix it
Jasminda: Are you actually trying to do Y? If so, you shouldn’t do X, you should do Z instead
Argh, this makes me so stabby. These days 90% of Stack Overflow "answers" are of this form, where the respondent does not respect the possibility that the questioner knows what they are asking and why. It is not always a sunk cost fallacy, where the questioner "might be attached to the steps they’ve taken so far" as the article states. That's also condescending!
- zabzonk 6y ago> George: I’m doing X, and I got this error, how do I fix it The question should be "I want to do A. I have tried doing it using X, but it doesn't work. Can you help me find a better solution?" The key is knowing what you want to achieve - which is A.
- AnIdiotOnTheNet 6y agoI have tried this in the past and then the answer becomes "why would you want to do A?".
- rzzzt 6y agoTo achieve Y, of course.
- drran 6y agoWell, there are multiple ways to achieve Y. I prefer way B, because it faster/cheaper/simpler/more durable/etc. than A.
- ZephyrBlu 6y agoIf they're trying to gather context, I understand asking a question similar to that. Though that exact question seems a bit pointed.
- zabzonk 6y agoPossibly you don't, but you must want to solve _some_ prime problem.
- BeetleB 6y agoOften, explaining what A is and why you want to do it is a ton of work, and my question (and the answer I'm looking for) is often very simple. Competent people don't like having to provide a lengthy justification for a simple question. In my experience, most people who push back and start saying "You really want Y" are simply not willing to listen to the story about A - especially if it will take more than 1-2 lines to explain it. I've found this to be the case both online and in person. As a somewhat related example, a decade ago I was building a PC and had been given a huge discount on a pretty powerful Intel CPU. I figured out all the parts (motherboard, etc), and went to a well known forum to post it and solicit feedback. Now the CPU was overpriced. You could pay 40% less and get another CPU that was almost as good. I knew this, but it was irrelevant as with my discount, I was getting it cheaper than the alternative. I posted my question, and acknowledged the price discrepancy, and almost all the responses were: Don't get that CPU, get the cheaper one. I made it explicit that I wanted a technical answer and not an economic one. I even said "Well, assume I'm getting it for free." The problem was that pointing out that I was getting my CPU even cheaper with a discount did not change anyone's response. Some people ignored it altogether. Others simply refused to believe I had a discount, claiming I was a wealthy newbie who was hell bent on paying full price just to get a tiny performance improvement and wasn't willing to admit it. Eventually some people took me at face value and answered my questions, but I spent a lot more time justifying my choice of CPU than on the actual questions I wanted answered. Also, asking: "I'm trying to do X. I'm aware of Z and I agree it's usually the way to go, but I have some restrictions such that Z won't work." Doesn't work. "I'm trying to do X. I'm aware of Z but I really want to see if I can do this with X." Doesn't work.
- srtjstjsj 6y agoCompetent people, nearly by definition, aren't asking questions on Stack Overflow. (We're all incompetent sometimes.) pcmasterrace fanbois arguing about their tribal alliance to CPUs is a different matter.
- tialaramex 6y ago> my question (and the answer I'm looking for) is often very simple If you're asking questions then confidence that the answer - which you do not know - is simple betrays the reality that you've become falsely confident of your understanding despite the fact that you don't know what you're doing or else you wouldn't have a question at all. Asking questions is a skill, whether you are asking the questions of a machine or of people. An insistence that everybody else is doing it wrong because you get unhelpful answers is a mistake nobody else can fix for you.
- jbjohns 6y agoCouldn't disagree more. The first thing that should always be done is answer the question as asked. Do what ever you want after that but anyone who doesn't should have their post removed. The issue is this: it is completely irrelevant why the person asking wants to do X or A. Stackoverflow and others are public websites and anyone who ever will want to do X/A will probably only find that page as an answer. It is beyond arrogant to assume anyone who could ever ask the question is just missing your guidance on what they really want to do. To be concrete, I find myself in these situations due to company restrictions that I simply cannot lift. So I need to do something I know very well shouldn't be done or fail (and someone else will do that or worse anyway). So I search all over the web and find a Stackoverflow page... that tells me why I shouldn't be doing it. And since it's been "answered" no one else will ever bother, and if I ask anywhere I get linked to that page.
- Swizec 6y agoAlways answer the question first. ”Here’s how you fix that error. But that’s an unusual situation and it sounds like you may have taken the wrong turn. What was your original goal?” Another frustrating thing is trying to teach when the asker is in hair on fire mode. Don’t do Socratic methods when there’s an emergency or the person is stressed about a deadline. Help them, then bring it up over coffee next week and explain the teachable moment. edit: Why the downvotes? Does HN really prioritize being unhelpful? That's weird
- BeetleB 6y agoI'm guessing you got downvoted because people tend to be attached to the Socratic method. There's a fairly narrow scope where it is a good idea - particularly when there's an understanding on both sides of mentor/mentee. In other cases, it sometimes works, and sometimes goes south. I've noticed that it's fairly common for people to resent the Socratic approach being used on them. Probably they think that you're assuming a teacher/mentor role (and this may not be your intention), and they want to keep it as a "colleague" role. Whatever people's intentions/interpretations, the Socratic method backfires a lot. Every one I know at work who is heavy on it has a number of colleagues who refer to him as "arrogant" behind his back. I remember the first time this happened, I was quite taken aback because I knew the person quite well, and he was anything but arrogant. But by using the Socratic method, people felt he was assuming a superior role.
- ZephyrBlu 6y agoThis is a shame to hear. I like the Socratic method and think it's the quickest way to get on the same page with someone. I also don't see any problems with someone probing what I'm doing. How can they help if they don't understand what I'm trying to achieve?
- srtjstjsj 6y agoSome people are anti-intellectual or are fearful and defensive at appearing less competent, perhaps out of fear that they will lose status or their job
- maaarghk 6y agolost way too much time the other day trying to figure out how to do encryption for a legacy PHP application. apparently it's incomprehensible to stack overflow writers that there are reasons i might want to know this beyond "implementing an unsafe login system". that said, this is talking about coworkers so maybe it is more appropriate when you can go back and forward on it
- kqr 6y agoThat's a misconception. The respondent absolutely respects that possibility. It's just virtually never the case. If anything, your type of criticism does not respect the low effort involved in almost every question asked. There's a bit of Dunning-Kruger to this too: the stupidest of questions will come from people who are absolutely convinced that in their case The question is warranted. It's just practically never. When one in a thousand misguided-sounding questions is legitimate, the only sensible thing to do is to assume all questions that sound misguided are. Then it's up to the person asking to be clear in why it's not. (Not to mention that clarifying that also tends to reveal other meaningful constraints on the answer.)
- jeffbee 6y agoA good thing to do if you think a question is "low effort" is just ignore it instead of assuming your own superiority.
- TeMPOraL 6y agoThe case of questions on public boards is different, because those also serve as reference for future people with the same question. Places like SO in particular exist not just to help the person asking, but the countless thousands who will find the question through Google search. In those cases, if you do the "looking at your context, did you mean Y instead of X" substitution, your answer will be still attached to a "how to X" query, and will frustrate a lot of people who may have a legitimate reason for doing X.
- nicoburns 6y agoIMO one of the best things about Stackoverflow is that it helps all the other thousands of people who thought they needed to do X but really needed to do Y. Having the answer for "how to do Y" under the correct label would be useless to these people because they'd never know they needed to do Y. If you really do need to do X, then explain why clearly in your question and you'll likely get an answer for it. And of course SO allows multiple answers, so we can have both the technically correct and the not technically correct but still useful answers.
- 6y ago
- ape4 6y agoYes on Stack Overflow, how can do do this in javaScript? Oh you need to download this library.
- jvns 6y agothanks for pointing out the "might be attached to the steps they've taken so far" line -- that is condescending, and I've fixed it to make the point I was actually trying to make (don't be condescending! :))
- ChrisMarshallNY 6y agoSO has helped me to ask questions well. It doesn't always prevent the patronizing, snippy slaps, but helps a lot. I've asked almost twice as many questions on SO as I've answered. It's a valuable resource to me, and I appreciate it. I do try to give back, and usually try to paraphrase questions that I'm not sure about, like "If you are trying to get X working, then here's how I did it." I've learned to try to remove as many "you"s as possible, and keep it focused on my experience and point of view, qualifying it as such. It does, sometimes lead to people accusing me of "Making it all about you," but it also removes elements of judgment.
- bonoboTP 6y agoWell, it's hard to tell apart, because people are not good at communicating their situation. In some cases I'm really just grasping in an unfamiliar territory and I would appreciate overall guidance of "you're holding that from the wrong end", big picture view of how things actually work and fit together instead of the twisted ways I may have come up with. At other times, I'm already quite familiar with an area and I'm trying to fix some rare case where I really need what I say I need, because I know the usual way, but in my case it won't work and having read up on some bug report discussions, I'm certain I will have to make a certain workaround work and it will require something unusual, but possible. It's just like how a help desk technician will ask me to turn my router off and on again, even though I'm a power user. It is because everyone, especially ignorant people think they know what's wrong, and they are never mistaken (just read /r/talesfromtechsupport). If you want to get past this, make sure to write in a way that's uncommon from ignorant people. Include what you have tried, what makes your case special, write with good spelling and formatting, use the technical terminology right to show you are experienced etc.
- jagged-chisel 6y ago> ... big picture view of how things actually work and fit together instead of the twisted ways I may have come up with. I can seldom find anyone with this answer at work. It requires that I read up on the tech/product being used, then exploring the repository for the configuration and code, asking six or seven people who have committed recently for their perspectives on why we're not doing what's in the docs (they don't know, they just followed the pattern and have no idea where other parts of a system rely on this particular thing...) Ultimately I discover that the diagrams on the wiki are outdated by several years, so, in text on that page, I note the differences. Then I discover that one of the first people I talked to were indeed The Subject Matter Expert who just can't be bothered to explain (or can't admit they don't know...)
- jagged-chisel 6y agoI really like when it continues thus: George: I am not trying to do Y. I'm trying to do V, and the path to V requires W which necessitates X. Jasminda: *crickets* In other words, Jasminda doesn't have an answer to the problem. I can only guess at Jasminda's motivations.
- hyperpallium2 6y agoAre you actually trying to [hammer a nail]? If so, you shouldn’t use a [screwdriver], you should use a [hammer] instead. EDIT code formatting now wraps on mobile!
- deleted 6y ago[deleted]
- drran 6y agoWhy not just file cross on the nail and make thread? In this case, screwdriver will work, so no need to buy hammer for one nail.
- cratermoon 6y agoWhat if you don't have a file?
- atoav 6y agoWhich one could easily address when formulating an question by making clear why this approach is taken (and who knows even if you know what you are doing, there might be really a better way to do it somebody discovered).
- strathmeyer 6y agoI always thought of it as telling everyone you are stuck in a hole with no ladder, and everybody tells you that you need to use a ladder.
- cratermoon 6y agoThe X/Y problem is a real problem, though. http://xyproblem.info/ http://xyproblem.info/