I'm not sure I understand the first question - can you clarify?
As for the second question, I think it's an important problem to acknowledge. The idea that a resource could be "best", if only you overlook the abusive garbage along the way, is a pretty poor example of "best".
I'm not a zealot or a purist - I don't think we need to throw out every tool or resource created by someone who turns out to be a jerk. There are some that we can afford to do without, where there are good alternatives - and there are some, like JavaScript, that are pretty much impossible to avoid.
The key, to me, is that we have open conversations about where we see harmful behaviors. Hero worship isn't called for, nor is demonization. But openly acknowledging problems lets us make better choices about the tradeoffs we want to make.
I like your perspective and will work to incorporate it in my own approaches to creating documentation, training, and instructions.
My first question was about finding good example ideas for documentation (in cases where having an example helps) without a wide viewership of the work. Upon going through your slides again, however, I see that the answer may lie in identifying my own biases and thinking about how to make examples from real world and more shared experiences, in a respectful manner. After all that, practice and getting feedback helps, I'd imagine. Did I get that right?
Ah, gotcha! Yeah, I think if I were going to set a goal for a longer version of this talk, it would be to provide more concrete examples of what's working well. Two challenges with that - first, it can be hard to find exemplary work that stands up to being blurbed, and second, I'm reluctant to name names. There's no one right approach, except for people to work actively to be more inclusive. What that's going to mean differs from person to person and audience to audience, and I'd rather talk about approaches than products for that reason.
For further actions, you may consider blocking this person and/or reporting abuse
Thanks!
I'm not sure I understand the first question - can you clarify?
As for the second question, I think it's an important problem to acknowledge. The idea that a resource could be "best", if only you overlook the abusive garbage along the way, is a pretty poor example of "best".
I'm not a zealot or a purist - I don't think we need to throw out every tool or resource created by someone who turns out to be a jerk. There are some that we can afford to do without, where there are good alternatives - and there are some, like JavaScript, that are pretty much impossible to avoid.
The key, to me, is that we have open conversations about where we see harmful behaviors. Hero worship isn't called for, nor is demonization. But openly acknowledging problems lets us make better choices about the tradeoffs we want to make.
I like your perspective and will work to incorporate it in my own approaches to creating documentation, training, and instructions.
My first question was about finding good example ideas for documentation (in cases where having an example helps) without a wide viewership of the work. Upon going through your slides again, however, I see that the answer may lie in identifying my own biases and thinking about how to make examples from real world and more shared experiences, in a respectful manner. After all that, practice and getting feedback helps, I'd imagine. Did I get that right?
Thank you Julia!
Ah, gotcha! Yeah, I think if I were going to set a goal for a longer version of this talk, it would be to provide more concrete examples of what's working well. Two challenges with that - first, it can be hard to find exemplary work that stands up to being blurbed, and second, I'm reluctant to name names. There's no one right approach, except for people to work actively to be more inclusive. What that's going to mean differs from person to person and audience to audience, and I'd rather talk about approaches than products for that reason.