How Group Chat Ruins Writing
Slack, and Group chat in general, ruins the most interesting property of writing, that once written, it lasts forever. This is why it's asynchronous, because it doesn't matter when you read it. By simply putting it in a Newsfeed, you're basically saying, "only new stuff maters" or in other words, "I'm binding this information to this point in time" which is good because it's tied to something, but has the problem of the fact that time is always moving which means that information will always become less and less easy to access the older it is.
Think about it, the Infinite Scrolling of chat means that older = more scrolling. We all like to scroll a little but after about 5 minutes of scrolling, you'll probably just give up and ask someone. This happens not only because our hand gets tired, but our brain also gets overwhelmed with all the information you're scrolling past.
All this is okay when there's very little movement on a Newsfeed, but in Slack there's generally a lot, even if it usually comes in bursts.
Also, it's being stored in a unstructured Messy drawer of communication, which makes things very hard to search for, and even harder to find unfragmented.
Why so much information? Because Slack encourages dumping of information in all the wrong places.
Backlinks: