5 ms·
I find that Slack creates worse "accidental" documentation than some other forms of communication. Prior to my team's adoption of slack, major decisions/design
by Slansitartop 9y ago
I find that Slack creates worse "accidental" documentation than some other forms of communication. Prior to my team's adoption of slack, major decisions/designs were usually documented in an email at some point, because they needed to be broadcast. If you can find that email then you have a fairly good self-contained resource for understanding whatever it was about.
Slack is easy and it's broadcast, so some people use it preferentially whenever they need to broadcast. However, the form that it takes is lines of text barfed out and interleaved with unrelated lines of text. There's no summary metadata (like subject lines), there's no organization except time, people put very little thought into what they type so it's at best rough draft form. It's hard to search, and even worse, your team or organization may be hip but cheap, and just get the free version that disappears your message history making search moot.
In short, we used to get better documentation for free, now we get none. Sometimes, old emails can be immensely useful in trying to figure out why something was done, or recovering old understanding and history.
- ebiester 9y agoHow many emails just ended up going to a limited distribution list? Worse, many email systems have a retention period. (This is also a problem with Slack, mind you.)
- Slansitartop 9y ago> How many emails just ended up going to a limited distribution list? Worse, many email systems have a retention period. (This is also a problem with Slack, mind you.) I'm not saying that email is perfect and doesn't have its issues, I'm just saying Slack is worse. The kind of use case I was thinking of is myself and others searching through our own personal archives for stuff (which people at my company use to get around server retention policies). That works with email but not with Slack.