I assure you you have never worked with a shittier colleague than someone who had left Expensify, as per the way the CEO spoke about them post-departure.
Years later I had drinks with my successor and learned I was actively blamed for things I’d fought mightily against.
I’m going back to vacation. If people still care when I’m back I’ll do a thread of Expensify Stories.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I often say that you should sponsor @LastWeekinAWS because you should. @davidcheal took me seriously and filled out the form!
I read his pitch, chatted with him a bit, declined to take his money, and have his blessing to deliver my feedback via Twitter thread. Let's begin.
First, I don't usually see the sponsor forms; it was passed to me. There's an editorial firewall!
Second, I won't take people's money if sponsorship won't help them.
David's product is thermite.red. Sponsoring me won't help him.
You're greeted by a mountain of text. People never read nearly as much as you'd think they would. The tagline ("meaningful insight into AWS usage") is half of the AWS partner network and a third of their own services if we're being honest.
Given that my daughter has broken her arm and Twitch / Amazon infosec have broken my heart, I distract myself from both with a thread devoted to answering this question, because I've lived it.
It's Day One, and you're the first DevOps hire at a startup. A bunch of developers probably interviewed you and almost passed on your hire because you suck at whiteboard algorithms; you saved it by whiteboarding AWS architecture on the fly.
What do you care about? Spoiler, it is absolutely not the bill. A bunch of developers have been running the infrastructure.
Be nice! They built something that's succeeded well enough to hire your ass; they don't deserve your scorn or mockery.
One of the hands down most sobering conversations I’ve ever had was with a bunch of Very Savvy Investment Bankers about what exactly a total failure of us-east-1 would look like economically.
The *best case* outcomes closely resembled a global depression.
That’s comfortably within their probability models for “a US civil war.” They’ve drawn up maps that show likely sides for such an event and they plan accordingly.
These people get paid significantly more than most engineers do to consider risk.
This is why you’ll not find even the most die-hard all-in cloud customer who’s publicly traded who doesn’t have “rehydrate the business” level backups either on-prem or in another provider.
While I do enjoy Twitter, I believe it's important to "own my platform." As such, Twitter's not material to the functioning of my business.
But I do talk to a lot of folks here, and a "subscribe" button for @LastWeekinAWS in my profile can't hurt anything...
I started by emailing @revue and checking their Terms of Service. As of today, there's nothing against using their sign-up function and exporting the list to another platform unless I'm directly monetizing the subscribers via subscriptions.
And now, a thread of Ancient Sysadmin Wisdom: an incomplete list of things we have learned from decades of outages.
"It's always DNS." Yup. Everything relies upon DNS, those relationships are non-obvious, and some things like to cache well beyond your TTL.
"If an outage lasts more than ten minutes, it's likely to last for hours." Yup. Usually related to electric power, but this is a good rule of thumb for "do we activate our DR plan" decisions.