So you might think that I'd turn this into a database joke, but it gets at something more interesting: the philosophy of failing over. A thread informed by Ancient Sysadmin Wisdom!
Back in the Olden Days of Datacenters, when sysadmins knew C, "serverless" meant that Dell hadn't shipped an order on time, and "Kubernetes" held as little meaning as it still does today, the question of how to keep sites up and running in highly available configurations arose.
It turns out that in single data center environments, you'd have all kinds of equipment; "phantom" routers (a fancy word for "standby") that checked constantly to see if the primary was offline; if so it would self promote.
It’s high time @PolyworkHQ added some features. A thread…
Let me endorse people for things. When they're late to a meeting with me, I can endorse them for "time management." Rude to me on Twitter? You're now a Sharepoint expert.
Offer more clarity in badges. What category does unpaid emotional labor fall under?
An observation on legacy: I have never once heard a story about Jeff Bezos that made me say "he seems like a nice person."
@aselipsky? Too many times to count. @ajassy? Seen it myself firsthand.
But never Jeff.
You can never get a complete picture from the outside. I get that.
But you can absolutely get glimpses of the real person behind the public persona by talking to the people who've worked with them. Given enough data points, you can tie them together into a reasonable story.
The question is "how do you want to be remembered after you're gone?"
For me, I really hope the answer to that question isn't tied to my job, but instead the people I've encountered along the way.
I can't very well do it myself. At The @DuckbillGroup, our clients these days start at ~$1 million a month in spend or so. I'm very hesitant to give guidance to small accounts based upon what large ones are doing. It's a very slanted view of the industry!
That said, the data I'm seeing in here tracks with what I'm seeing in our client environments. As the post says, "this aligns with other cloud consulting organizations @getvantage has spoken to." We're one of them. They're spot on for the big items.
The big problem that enterprises have is that the @awscloud bill is a game of Corporate Telephone between the person who receives the bill but has no context, and the person who can impact the bill who's five nodes away.
"Let's make sure that last person can never see the bill!"
Enterprise cloud deployments have their own fair share of problems, don't get me wrong. I just have a very hard time believing that "too many of our employees are looking at the bill" is in that list.