In tonight's thread, incoming @awscloud CEO @aselipsky gets to learn who I am, along with anyone else new to my nonsense. This might take a few tweets.
Around the time @aselipsky was leaving @awscloud I was starting the consultancy that eventually became The Duckbill Group. We fix AWS bills for large customers, and also have a "media" division. Our mascot is Billie the Platypus, who is dangerously unstable and frankly scares us.
Those scare quotes around "media" account for the @LastWeekinAWS newsletter, blog, and podcast, meanwhileinsecurity.com, and the non-snarky interview podcast "Screaming in the Cloud" to which @aselipsky has an open invitation. I also tweet actively and aggressively. Oh dear.
If someone can tell me @aselipsky's birthday, we have Spite Budget reserved for a thing.
Yes, I said "Spite Budget." Most companies don't have one of those. Most companies also don't need one to hire a troupe of opera singers to cover a parody of "Where in the World is Carmen Sandiego" to wish @werner a happy birthday, either.
I'm an analyst, engineer, marketer, writer, consultant, public speaker, stand-up comic, and cloud rodeo clown. I'm not nor have I ever been an @awscloud partner, employee, or member of the press.
I can describe virtually every AWS service in some depth off the top of my head.
Onalytica claimed I was the Greatest Cloud Influencer in the World. The New York Times christened me an "AWS Gadfly."
Someday @awscloud will realize that while I have many odd talents, I'm probably not immune to crossbow bolts.
Every year we do a charity t-shirt fundraiser for re:Invent. This year's is already in the planning stages, and will benefit @826national.
I have many running gags / deeply held beliefs. Some of them include:
* AMI has three syllables
* AWS is bad at naming things
* Route 53 is a database
* I'm the Head of AWS Marketing in my spare time
I suspect the most aggravating thing about me is that I'm usually right about a customer pain or problem, so you can't entirely write me off as some random internet troll; I have an uncanny ability to "Be Right A Lot" and point out the gap that got missed. We share customers!
The only hard and fast rules are that my opinion isn't for sale, and I absolutely will not punch down.
I think that about sums it up. Friendos, what have I missed that @aselipsky should know?
Ah, right! In 2019 the "AMI has three syllables" shirts were $10 more, because there's a cost associated with being wrong.
A few other points have been raised! I'm a father and husband, which are the most important hats I wear. I don't usually involve them in my shitposting extravaganzas.
I have a recurring theme of "happy, and with your mouth open" in selfies. I look forward to taking one with you, @aselipsky.
You can subscribe to my email newsletter at LastWeekinAWS.com. It's generated by an architecture that looks like a shitpost but I swear to you is real; I didn't say I was a *good* engineer.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
How do we interview? Well okay. We're still learning. This is how we approach hiring for Cloud Economists (other roles vary and are available at duckbillgroup.com/careers/). There are six steps.
Step 1: So you apply by filling out the form. Next, @mike_julian goes through and screens out poor fits.
(He has no job more important than hiring.)
What do I mean by "poor fits?" No AWS cost optimization experience, inarticulate answers to the questions in the application, etc. We never "shame" folks for it, we just move on.
Nobody should ever be made to feel like an asshole for applying for a job, full stop.
Having reviewed the counteroffer that @vPilotSchenck's dev friend sent, it's very much a "bullet dodged." There was nothing egregious about it, and the company comes off incredibly poorly as a result.
The response was reasonable. The edge case I’d have understood would have been an emailed counteroffer that made the employer question the candidate’s professionalism or judgement.
I’m talking “8x market rate” or opening with “Dear Shitpoodles.”
The company now has spent more than the salary difference just getting to the offer stage, so it’s dumb financially. And they’re in a small sector so it’s reputationally moronic.
So who is @aselipsky? He left @awscloud for @tableau shortly before I entered the space (presumably because he was so disgusted with QuickSight that he wanted to ground them into the pavement as a core focus), so I'm as puzzled as you.
A thread!
We know he was one of AWS's first VP hires--he came aboard in 2005 from RealNetworks where he was the VP of Buffering.
Apparently he's serious, businesslike, and inside of @awscloud he's almost universally liked.
In other words "so much my opposite that if we ever shook hands the resulting explosion would destroy everything within six miles."
“Telemedicine” is a $100 billion market that will be worth every penny when you need a quick excuse for your roommate when they walk in on you showing your butthole to your webcam.
Site Reliability Engineering is just DevOps with better gatekeeping, which is just sysadmining with a better paycheck.
The first donation is in. Yay, the system works. That's because @charitywater clearly doesn't use a service mesh, which is the first victim of the snark.
Service meesh are fundamentally thin layers of abstraction on top of DNS, which is a database. The reason for this is purely to shut up the "it's always DNS" brigade. Now it's the service mesh which nobody understands either, but at least this time they're honest about it.
“The Duckbill Group” is next. Sweep away the fancy language and the marketing; what you’re left with is “Dramatic Readings of Excel Spreadsheets.”