Stage 0: You have an idea. You fit in the free tier.
Stage 1: You get a pile of Activate credits (anywhere from a pat on the head to $100K, though there are exceptions). This counterintuitively helps set you up for failure; if it's "free" to you, you don't practice good early hygiene.
Stage 2: OH SHIT. Your credits ran out, now you have to spend actual money.
Stage 3: You get a call from whomstever your AWS Account Manager is for that day's morning shift offering you a discount in return for a commitment.
"Sure, but why?"
"You're spending a million bucks a year with us."
Stage 4: Whomstever was handling your costing work on an ad-hoc basis needs supplementing. Possibly because of overwork. Possibly because they rage quit. It's time to look at building a cross-functional team. Possibly full time, possibly not.
Stage 5: You've got a team that focuses on this. Finance folks, a dedicated cadre of efficiency engineers, etc. You spend millions on them because they justify their entire annual budget by lunchtime on their first day.
So those are the growth / pain stages in a general sense. Specifics are of course more nuanced, and the "why you care" is more important than the dollar figure.
The first thing we ask clients here at The @DuckbillGroup is "why do you care what the @awscloud bill is?"
*Theoretically* there's a Stage 6 wherein @awscloud names a building / conference / service after you and multiple execs mistake @aselipsky for your account manager, but that is... uncommon.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So many years ago, when my humor was significantly more sophomoric, I had the “cloud to butt” browser extension installed.
It replaced the word “cloud” with “butt.” Suddenly @RedHat’s site was talking about public and private butts, which admittedly makes a lot more sense than whatever the hell it’s talking about now.
I was embedded at a client site for a while, and I replied to some email or another. The client manager responded with what might possibly be the most flustered email I’ve ever read, apologizing for his previous message.
Every time that I've looked at them prior
I found two big things to correct:
The first rooted within architecture
The other its shitty DX
For the former it seems kinda squirrelly
For a database to think that it's somehow a queue
And the latter with console or CloudFormation
ERROR: ROLLBACK_IN_PROGRESS: FUCK YOU
So an anonymous Twitter person DM'd me this morning with a scenario. "I work at a large cloud company that makes inscrutable naming decisions, and I have an offer elsewhere for 35% more. Should I take it?"
Oh good heavens yes. A thread...
I hopped on a call with them and proceeded to firehose a bunch of career advice in their direction. I took a few notes and here's the gist of it.
No one is going to have your interests first and foremost except for you. You owe your employer a duty of care, and a duty of confidentiality, but you don't owe them loyalty.