7 ms·
How to answer questions in a helpful way (2017)
- khalilravanna 6y agoDocumenting FAQs is so important. I found the private StackOverflow tool to be really useful for the documentation of all sorts of questions. From debugging (“What do I do when I get paged with a critical error?”) to process (“How do I create a good pull request?”) to tooling (“What’s the easiest way to run unit tests in Visual Studio Code?”). It’s a big force multiplier if you’re in a scaling organization.
- pbalau 6y agoPrivate StackOverflow? Can I have a link, this sounds interesting
- strombofulous 6y agohttps://stackoverflow.com/teams https://stackoverflow.com/teams
- thedanbob 6y ago> I’ve worked on actually pretending not to be surprised even when I actually am a bit surprised the person doesn’t know the thing and it’s awesome. I try to do this too but sometimes I forget. However, I find that acting surprised is ok if you then show your excitement to tell them about the thing e.g. xkcd.com/1053 The key is to not express “You don’t know about this? What is wrong with you?” but rather “You don’t know about this? You’re going to love it!”
- baby 6y agoI think this nyc workshop place (recurse center?) had a rule about not doing that.
- JoshTriplett 6y agohttps://jvns.ca/blog/2017/04/27/no-feigning-surprise/ https://jvns.ca/blog/2017/04/27/no-feigning-surprise/
- aspaceman 6y agoYeah it's ok to feign surprise if you use it as a "Wow I feel lucky to show this to you." Some people genuinely mean it that way, and if you can communicate that's your intent, I think that's fine. It's exciting when someone hasn't heard about something really cool. And it's nice to feel like you're being brought into the club.
- nurettin 6y agoI just trust that people aren't dumb, that they did all they could and had a solid plan up until they got stuck which prompted the question. Then I empathize with their situation and try to pinpoint what piece of the puzzle they are missing. Usually it is just a tiny bit of information that gets them going. Others prefer to go through the whole "rtfs rtfm make a test case and how to be a hacker faq" stuff.
- jeffbee 6y agoGeorge: 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 ago
- flaxton 6y agoThis is a very helpful reminder ;-) It’s not about you or about showing how smart you (think you) are, but about being helpful and helping others to grow.
- baby 6y agoThere’s something else: if someone (or more people) keep asking you questions that seem maybe easy for you, then you need to make a better effort onboarding people and documenting clearly what is going on.
- ChrisMarshallNY 6y agoI just love reading her stuff. She must be a joy to work with. Our industry needs as much humanity and empathy as possible. She sets a high bar. It goes without saying that she's obviously absolutely brilliant, but she's also energetic, curious and polite.
- malwrar 6y agoExample question from the article: > “I’m seeing errors on the site, what’s happening?” What was the error? What were you doing when the error occurred? How can I reproduce the error? These sorts of one-sentence questions with no context are the worst, because when you come across them and decide to help out they force you to fully engage with someone who pretty much just wants to be given a fish rather than be taught how to catch them. I've even participated in communities where the expectation seems to be "give me the code I need to solve my problem. now.", and I'll be honest after awhile of experiencing this I got burnt out and now just reach for RTFM responses and get back to what I was doing when I encounter (what I perceive to be) low-effort questions. I guess my point is that, if we want to tell people who give their time for free how to properly answer questions such that the feelings of the asker are respected, we need to have some discussion of what to do when that's evidently not the case. When I read this article, I find myself wondering why I should have these sorts of expectations unconditionally placed on me by someone who is asking me to make time for them. I feel like a discussion about respectful knowledge exchange aught to encompass both parts, lest either side come off as entitled to a free lunch.
- owlie 6y ago> if we want to tell people who give their time for free how to properly answer questions I see this article more as a resource for curious people who want to improve their interpersonal skills and provide more helpful feedback. (I especially feel this way based on the author's blog, and their activity on Twitter! They create a lot of kind, supportive, educational material.) I _don't_ see this as a prescriptive piece trying to impose constraints on other people's behavior. If the specific advice doesn't resonate with you, then that's okay!
- d0paware 6y ago> To start out with – sometimes the people asking you questions don’t respect your time, and that sucks. I’m assuming here throughout that that’s not what happening. I'm curious, how do others handle interactions with people who don't respect your time? I'm talking about coworkers who do not improve in their question asking ability after you've gone through the processes the article describes multiple times in good faith. People who Slack or email several people in parallel, waiting for the first reply to come back. I've found that being honest with problematic coworkers - i.e. asking them face to face to invest more effort - is a risky thing to do. Even as an authority figure on the team, it's easy to develop a reputation for being an asshole, even if you're as polite as possible. Instead, I save the feedback for my manager with concrete examples, and have them deliver the bad news. A lot of managers need to receive overwhelming feedback that the offender is doing this, so you may need to prompt them to ask other members of the team to solicit feedback. Some people are too nice to bring it up. Even then, it's notoriously hard to correct behavior in these individuals and even harder to get them off your team. So when everything else has failed, I ignore messages from them for maybe 2-3 days, and then reply back with "sorry, did you still need help?" and continue stonewalling them until they give up. It's most effective when you can get everyone on the team to participate so that the person is forced to pull their own weight.
- js8 6y agoI would say, respond that you don't know the answer from the top of your head (assuming that's the case), and politely refer them to read the documentation (or experiment). If the documentation doesn't exist, consider creating it. If they ask same questions again and again, suggest them to take better notes. I think complaining about it is counter-productive. Force them to do the legwork, explain that it is primarily their task to do research on a topic.
- purplecats 6y agomy coworkers purposely answer questions bad so that the knowledge stays with them and increases their job stability. it's sickening.