Live data from Hacker News

Slack’s Incident on 2-22-22

slack.engineering

181–183 of 183 posts

Re: Slack’s Incident on 2-22-22

#181

Earlier quoted context omitted.

Quoted post unavailable.

> engulfs the worker inside a dead-eyed grunt culture, featuring an endless spree of work-life balance destroyers. It might be great for people who ask for things from others, but for the people who have to actually do the thing being asked of them, Slack is a nightmare world. I think it depends on the organization and how you use it. In a previous role I would’ve agreed with you. People expected you to reply at all…

Nah, nothing can save a work culture when it utilizes Slack for anything. I have been on both sides of the relationship in the Slack-based work society. It always ends up yielding the same outcome, no matter if I am a manager, an individual contributor, or even an outside contractor.

There are always going to be a couple of people in your unit who run the show, who make all the animated GIF posts, to make all the slackbots that don't do anything. They always use Slack to gain undue notoriety within their firm. Slack caters to these people because these people tend to have the controls over the purse.

It's a terrible thing to do to a business, to force Slack upon them. You cannot blame Slack for making this dang product, but you sure can blame the people who consume & purchase the service without even once thinking about the well-being of the employees.

Re: Slack’s Incident on 2-22-22

#182

Earlier quoted context omitted.

> engulfs the worker inside a dead-eyed grunt culture, featuring an endless spree of work-life balance destroyers. It might be great for people who ask for things from others, but for the people who have to actually do the thing being asked of them, Slack is a nightmare world. I think it depends on the organization and how you use it. In a previous role I would’ve agreed with you. People expected you to reply at all…

Nah, nothing can save a work culture when it utilizes Slack for anything. I have been on both sides of the relationship in the Slack-based work society. It always ends up yielding the same outcome, no matter if I am a manager, an individual contributor, or even an outside contractor. There are always going to be a couple of people in your unit who run the show, who make all the animated GIF posts, to make all the sla…

I can't say ive seen any of what you’re describing despite using slack since the early days across several organizations. I know that my experience is just that, but you might want to do a little introspection. this sounds very pessimistic and a bit paranoid.

Re: Slack’s Incident on 2-22-22

#183
post #171

Earlier quoted context omitted.

"I treat memcached in infrastructure as a very stable service." I run memcached at a large scale. You are totally right. Every other year we will find ONE bad memcached node down. We use nutcraker instead of mcrouter for consistent hashing to each memcache node. Once i read "We also run a control plane for the cache tier, called Mcrib. Mcrib’s role is to generate up-to-date Mcrouter configurations" -- I was like oooo…

Our underlying hardware (AWS) is nothing like this reliable. We see regular (several times a year) failure of racks of machines or whole DCs. Across the whole fleet (all services), we lose 1-10 servers per day as a baseline. Major events are then on top of that and can impact thousand of hosts at once.

What service is this?? This must be huge.
Post reply on HN