4 ms·
I love this topic, too. And this is so true: > I think one thing that's needed to establish a culture of written communication is getting rid of any cultural e
by klenwell 6y ago
I love this topic, too. And this is so true:
> I think one thing that's needed to establish a culture of written communication is getting rid of any cultural elements that allow people to use the avoidance of reading and writing as an expression of power.
I'm not in love of the idea of assigning a team librarian or scribe. I really want it to be part of the culture. Up to the executives. But if someone could demonstrate it works (and how it works), I could be persuaded.
One rule I try to impress on my team: you should be answering common questions whenever you can with a URL rather than a wall of text. That URL can link to a wall of text (or hopefully something a little better structured). Ideally in our wiki. That beats eight different people answering the question eight different ways. Or the same person answering it eight times in slightly different ways.
- toast0 6y agoIf you want to have ok documentation, making everyone do it, can work. If you want to have great documentation, it's hard. Very few people are going to be great at solving problems, great at expressing that in new code, great at maintaining existing code, great at debugging, great at testing, great at deployment, and great at documentation. Specialization makes a lot of sense in many contexts, and writing documentation is one of them.