,
13 tweets,
3 min read
Read on Twitter
I was summoned in a thread about the 2017 S3 failure. You guessed it--it's threadin' time! (1/13)
First, Karan's great. I'm not trying to say he's being obnoxious, insulting, etc. He isn't. But he is wrong. The internet didn't turn into me. The internet turned into a bunch of spoiled childish shitheads. (2/13)
I saw a lot of crappy behavior when S3 went down. People implying that AWS was incompetent. People berating the @awssupport and @awscloud accounts on social media. (3/13)
I get it. It impacted your business, your life, etc. Outages are stressful, but I've yet to see a single case where turning into a huge asshole made a crisis better. (4/13)
I'm snarky. I'm sarcastic. But I'm not intentionally mean, and if someone goes home at the end of the day depressed because I insulted them, then I've failed. I'm sorry. Save this tweet; reach out to me when I get it wrong. (5/13)
I've often referred to @azure as having potential "because Microsoft has 40 years of experience apologizing for software failures." People laugh, and think I'm making fun of Microsoft. I'm not. (6/13)
I'm being completely honest. Computers *break*! It's what they do! If you can't accept that, I challenge you to go have a chat with anyone from @gremlininc. (7/13)
The S3 outage wasn't, as it's often facilely reported, "someone making a typo." It was a typo, that wasn't bounds checked, that took down too much capacity too quickly, causing a restart that hadn't been tested, which in turn... (8/13)
You get the idea. You can read about it for yourself: aws.amazon.com/message/41926/ (9/13)
There's no such thing as a simple outage at this scale. A bunch of factors contribute, and the failure is of the process, not some random schmoo of an engineer who made a mistake that anyone could have just as easily made. (10/13)
If you've never caused a production outage, either you're very junior, or nobody's ever trusted you with production access. (11/13)
I talk a lot of smack about companies, but you'll never see me yell at them for an outage. (Data breaches are a separate thread.) (12/13)
So the next time a service provider takes an outage, be kind. Put yourself in their shoes. Look for the #hugops hashtag. After all, we're all in this together. (13/13)
