3 ms·
I have definitely worked in places where the times right before and right after a change freeze were the most unstable, so that could be it. However, as others
by cratermoon 6y ago
I have definitely worked in places where the times right before and right after a change freeze were the most unstable, so that could be it. However, as others have mentioned, it's pretty early on the west coast of the US. Unless some engineer was up extra early (perhaps at the behest of an anxious project manager) it seems unlikely to be a release.
What it could be is some engineer somewhere coming in after the holiday, noticing a slightly flaky thing, and thinking, "I'll reboot/redeploy/refresh this thing so the flakiness doesn't get worse". Only it turns out the flaky thing was a signal of something else falling over. Or maybe the redeploy was the wrong version because of bad CI/CD, or maybe the person just fat-fingered it.
- savo92 6y agoOr unless that engineer was not in the US
- cratermoon 6y agoVery possible. I don't know what Slack's workforce distribution is. In places I've worked there have definitely been some incidents in US off-hours triggered by someone on the other side of the world.
- ikiris 6y agoMost releases are automated with time lockouts.
- cratermoon 6y agoIn what companies?
- ikiris 6y agoCompetent ones like those you'd hear about being down on HN. At least that how it worked at one FAANG
- londons_explore 6y agoIt varies a lot by team... I think it's common to have a single click "start" button to press. It's a good sanity check that a release isn't going to happen during a fire drill, outage, or strike...