And now a thread about the @awscloud Organizational Stages of Grief. Tag yourself!
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
 

Keep Current with Corey Quinn

Corey Quinn Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @QuinnyPig

16 Sep
I will now proceed to man-explain @colmmacc's truly excellent post at shufflesharding.com/posts/aws-sigv…, using smaller words.
"In the time it takes to read this sentence, the AWS Identity and Access Management (IAM) service will handle several billion requests."

@awscloud is kicking itself for making IAM free.
"I didn’t have a hand in designing the AWS SIGv4 protocol"

Do not blame @colmmacc for any of this.
Read 15 tweets
15 Sep
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.
Read 7 tweets
15 Sep
And now I join #amazoncareerday because they invited me. This is going to be glorious for someone. Image
So far the application process sounds like more work than the last full time job I had.
"Let's start by addressing the elephant in the room." Amazon's turnover? Comp issues? The non-compete agreements?

No, the pandemic apparently. Image
Read 19 tweets
15 Sep
AJ's thread here is rather compelling
It touches upon some big themes
I'm reading along and I'm agreeing
But I've yet to touch Dynamo streams...
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
Read 5 tweets
14 Sep
SQS, a simple queue
I do indeed have tips for you.
5 figure bill? It could be worse
In this thread I shall help in verse
Since SQS bills you per request
The naive approach is "use it less"
As general guidance, that mismatches
So instead put your messages in batches
We find this happens now and then:
batch up those items, up to ten
Buffer writes; savings are giant
(Assuming that's supported by your client)
Read 6 tweets
10 Sep
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.
Read 45 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(