- cross-posted to:
- hackernews@derp.foo
- cross-posted to:
- hackernews@derp.foo
A friend shared a post from someone else that was talking about this article. I’ve quoted the text from that post below:
This is a 1996 guide on how to help someone use a computer. It’s strikingly resonant with ‘how to be a parent’, or really ‘how to help anyone with anything’. A nice example of “the universal within the particular”
This is all great advice, but I do want to add that it’s mainly for beginners in one-on-one contexts, and not always appropriate when dealing with technical users in a group setting. For example:
It’s frustrating in online communities when someone asks a technical question and is met with an interrogation instead of an answer, on the assumption that they don’t know what they want to do. Not just for the person asking the question, but also for future people arriving at the thread with the same question. In some cases it really derails the conversation.
Hierarchical threads like on Lemmy or Reddit tend to be better for this than flat threads or chat channels, since it’s easier to isolate and ignore red herrings. One reason I hate Discord and Slack for tech support.
You’ll find that technical questions from experienced people tend to include “To do X, I’m doing…”. Basically for two reasons: They’re already accustomed to zooming out and looking for other approaches before even asking a question, aren’t lost in the weeds, therefore asking the question top-down is natural, secondly, because they can predict the inevitable “you don’t actually want to do this” answers if the approach is even a little bit off the beaten path.
Consider the flipside: Helpful people wasting their and your time teaching you how to build a flux compensator when all you wanted to do was make some coffee. Just buy a machine off the shelf. Interrogating, alas, is warranted in the majority of cases that’s why it became a thing in the first place because most people aren’t trying to engineer a novel flux-compensated coffee machine.
Excellent point. I often find myself torn between providing all relevant context to get ahead of this, and keeping my posts short enough that people will actually read them.