Slack: Other browsers require significant effort so we're focused on Chrome

Re:Slack: Other browsers require significant effort so we're... by teilo on Sunday February 04, 2018 @12:11AM (#16301460)

> I've been using slack for my jobs for years, and it wastes more time than saves. No real work gets done in a chat room, which is what slack is.

Speak for yourself. Our DevOps uses it extensively, and gets plenty of work done. It's been a great tool, has saved time, decreased ticket response time, and increased follow up. If we didn't have it, we would have to scramble to find something to replace it.

[ Parent | on HN ]

Re:Slack: Other browsers require significant effort so we're... by cannonedhamster on Sunday February 04, 2018 @12:36AM (#16301527)

The only thing Slack provided for the longest time was chat. Essentially it was nothing more than a decent, private IRC implementation. I'm curious what your DevOps team found as a pain point in communication. Were you just using email?

Slack now is a significantly improved tool that we use all the time for everything except large or external video chatting. It's a very nice tool for centralization of alerting, monitoring, etc. We'd find it very hard to move elsewhere as a company.

[ Parent | on HN ]

Re:Slack: Other browsers require significant effort so we're... by teilo on Sunday February 04, 2018 @12:12PM (#16303582)

We started using it when the API was already available, and tied in error alerts from our integration server on day one. We've added a lot more since then, among them jenkins, monitoring thresholds on our AWS instances, etc.

[ Parent | on HN ]

Re:Slack: Other browsers require significant effort so we're... by cannonedhamster on Monday February 05, 2018 @01:11AM (#16306955)

Yeah, we're in a similar boat using it to monitor Jenkins, Datadog, Zendesk, JIRA, and a whole slew of other things aside from chat. It's hard to find a better bang for your buck if your company is bought into the ecosystem.

[ Parent | on HN ]