3 ms·

My contribution to this debate is that it isn't a developer problem it's a "beginner's mind" problem, which I personally characterize as "empathy" Can one reca

My contribution to this debate is that it isn't a developer problem it's a "beginner's mind" problem, which I personally characterize as "empathy" Can one recall what it was like 15 minutes ago when you didn't know the answer, and how would you have changed the situation to foster the pathway that would have squared up the product's model with your mental model. No matter the product: library, webpage, physical tool, bureaucratic process, etc. If a human(s) made it, then managing the assumptions is a grade-A problem that requires managing throughout its lifecycle Developers love to complain about bad requirements, but documentation is where one gets to provide the requirements to the reader, thus, is an empathy management exercise

spondylosaurus 1y ago
People also call it "the curse of knowledge," and yeah, being able to empathize with the non-expert is both an ongoing effort and a learned skill. A lot of my job as a tech writer is basically acting as a shock absorber for user frustration in that regard, because when I need info from devs it's a constant struggle to get them to explain what they built—they often give descriptions that don't make sense unless you're already familiar with whatever they're talking about, which sort of defeats the purpose of a description. So I have to do all the teeth-pulling up front, and eventually get the necessary info, and then present that info in a way that actually makes sense to users.