3 ms·
Before 'Slack' I trained people out of asking me email questions by putting the answers in the wiki. At first I had to create the wiki pages to explain what wou
by hinkley 4y ago
Before 'Slack' I trained people out of asking me email questions by putting the answers in the wiki. At first I had to create the wiki pages to explain what would have been in the email, but over time people became self service. There are some negatives to this approach but mostly reducing certain classes of interruption are a good thing.
Wikis are precursors for dead tree documentation. It's both a place to store highly volatile pieces of information, and a place where you can start documentation, copy-edit it for months or years until it's just right, and then move the contents into 'real' documentation.
In the Slack age, we need a pipeline that starts in chat, moves to the wiki, and ends in capital D documentation. It wouldn't even have to be that hard. You could simply vomit out the contents, or you could try to be a little more sophisticated where you treat one participant as the author of the sections of the document and the other authors providing the copy for those sections. The goal is to rescue the contents before they disappear, either for real or just due to SNR.