@azure had a GOLDEN opportunity to pull a "we don't mine your data, we don't compete with you, WHO KNOWS what @GCPcloud and @awscloud do with your confidential cloud info!"
Instead they legit did exactly what their competitors don't, but we worry about.
An awful lot of people blaming @ubuntu here, but if AWS were willing to sell me a list of people who just had massive bill spikes? Sure I'd buy it!
If AWS would sell me information like that you would be best served by evacuating their cloud immediately.
Some speculation that the user spun up a @ubuntu image from a marketplace equivalent.
If you spun up my CoreyOS marketplace image and I did outreach like that, @awscloud would give me the choice of never saying that again, or being booted off of the marketplace. Trust matters.
The LinkedIn outreach is arguably the creepiest part of this. I mean, a cobranded email is still Not Terrific, but this is basically "Azure gave my name and affiliation to a third party and wished them 'happy hunting.'"
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I believe I owe the Twitter a thread on my "Rules of Shitposting." This is that thread.
It's in our Corporate Docs at the Duckbill Group under the more prosaic headline "Our Marketing Beliefs & Rules."
There are seven of them, and were collected by @mike_julian based upon the things I've said and we've ruminated upon.
Rule 1: Consent is required.
"The world is full of marketers and advertisers foisting things upon people without their consent. We don’t want to do that. Our marketing should always require consent."
I can't stress how important this is. The newsletter is confirmed opt-in.
Thanks for coming to work with us here at Trashfire Inc. Let me show you around the exciting aspects of our corporate culture!
Okay, you have your badge? You sure you got your ID back from the reception desk? ...sorry, the badge reader is on the fritz again. Try scanning it a few dozen more times. You've almost got it. There you go.
Sorry more folks aren't here to welcome you. This quarter everyone's heads-down on an all-company initiative: writing our performance reviews so we can all fight for the coveted 3% raises that top performers get. We do this every year.
"I hate my job, I'm going to quit and start my own company. How hard can it be?"
Oh so tremendously hard. A thread.
I said this a lot when I was consulting for an agency. "Hey they're billing the client WAY more than they're paying me; I should go direct and capture the margin!"
It's nice work if you can get it, except you can't.
Sales and marketing are actual skills. Customers don't generally fall out of the sky.
If you found a customer to go full time consulting with, you're basically an FTE without a raft of employee protections.
So this has been on my backlog for a while, let's get rid of it. @rseroter wrote an analysis of the various provider offerings' Cloud Shells. I haven't actually read it yet, but let's tear into it.
Let's start by disclaiming two biases. 1) @rseroter directs "Outbound Product Management" at GCP, so he's not exactly objective. 2) AWS's Cloud Shell came out 5 years and 2 months after GCPs, so if it's not "blow the doors off" better, then it failed.
He starts with @gcpcloud's Cloud Shell. I like how it's part of the same view, not a separate window. And you get 5GB of persistent storage to AWS's 1GB. Hmm.
Small typo there: there should really be a GIANT FREAKING ASTERISK next to "free." "Get started" drops me to the sign-in page which is also a bit disconcerting. "Create new account" is hanging out at the bottom.
The copy here could use some love. I'd be willing to bet the majority of first-time users aren't really clear on EC2, S3 they recognize from scary headlines, and "what the hell is a DynamoDB" is the DynamoDB team's motto.