> 'You can try to limit the use of Slack to avoid these problems. But you are working against Slack, not with it'. So, if I have a hammer, I shouldn't try to u

> 'You can try to limit the use of Slack to avoid these problems. But you are working against Slack, not with it'. So, if I have a hammer, I shouldn't try to use that hammer in a constructive manner, but should throw it away and find something that is universal for all of my tool using needs? Rather than using the hammer as a hammer? Sure, any team can screw up communication. I'd argue that many teams ship shit software in shit environments, and that adding slack is like adding 'devops' or 'agile': if your team sucks, it doesn't matter what tool you use, you're gonna suck. Adding new tools may even make you suck worse, because you now have 2 problems: poor comms AND a tool that doesn't fix that which you have to deal with. Slack is a hammer. And I have a shitload of nails to hammer in. I don't have ONLY nails, and Slack isn't my ONLY tool, and it's not appropriate for ALL THE THINGS. But your own argument is that you shouldn't look at it as the solution to everything, but then throw it away because it's not the solution to everything. Is it the tool for you? Apparently not! And that's fine. That doesn't make it a bad tool. Some of us have lots of nails to hammer in, and some of you have screws that need another approach (even if you could hit it hard enough to drive it home...thats probably non-optimal).