For large organizations, a forum/ticket model is a much better way to leverage organizational memory and knowledge. For small teams, and teams within organizat

For large organizations, a forum/ticket model is a much better way to leverage organizational memory and knowledge. For small teams, and teams within organizations, I actually think the Slack model does fine if people mute it. I'm one of those people that loves to help people with technical challenges and this was a big hurdle for me. Almost all of the problems in the article can be solved by muting and only checking during breaks. I don't think anyone rational would conflate productivity with availability on slack unless their job is to answer questions on slack. It's also just such an obviously bad idea to forgo documentation in favor of Slack that I'd say no rational developer would do that either. Those aren't problems with Slack, those are problems with lazy people who want to blame Slack for poor software development.