Another day, another "fuck you for paying us" from Google.
If you don’t think sharp edges like this on your consumer products shape opinions of your business (read as: cloud) products, you’re dead wrong.
(This is my “personal” account; it’s my 20 year old vanity domain for personal email; nobody else has an account on the domain. The only way to have a custom domain is to pay Google—which I’m normally okay with until I hit nonsense like this.)
If @IsForAt wants to seriously fix Google’s reputation, field a team of a dozen engineers whose sole job is to be customer ombudspeople who cut through Googly excuses with axes and solve things like this.
“Well it turns out we can’t easily fix this because what we do wouldn’t work under the Business privacy policy.”

THIS IS WHY THE TEAM IS ISSUED AXES! Fix that sort of thing IMMEDIATELY!

• • •

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

21 Jan
One of my favorite recruiter stories is how one once sent me an unsolicited anonymized résumé out of the blue (spam, basically).

It turns out it’s not exactly hard to figure out whose résumé it is. I reached out directly, interviewed them, and hired the person.
A bit more detail: I originally reached out to figure out if the person was aware their résumé was being spammed out.

“No! My god that’s awful!” We kept talking, they applied directly, and there you have it.
It’s true. That’s how I met / hired @setient.
Read 4 tweets
20 Jan
Let's go back in time and put on my Analyst / Marketing pants. It's years ago, I'm advising @elastic, and @awscloud has just come out with "Amazon Elasticsearch." This feels bad, since (as attested in court) they didn't give a heads up, and there's the danger of brand confusion.
First, I've gotta admit that I'm fighting a rearguard action in some ways. "Elastic Compute" predates the founding of the company and its trademark by a lot, and there are a bunch of other "Elastic" terms people equate with AWS.
In effect, the odds are basically zero that people already aren't equating our stuff as being an Amazon offering. I'm only half kidding when I suggest "Stretchy-Go-Findy" as an alternate name.
Read 10 tweets
14 Jan
This will sure show @awscloud! No way they'll be able to create Amazon Elasticsearch a... second time.
Yes. That is exactly the *point* of open source. Don't like it? That's valid! Don't go open source. But to claim that @awscloud and others are somehow doing something underhanded is just flat out incorrect. Image
As @vmbrasseur points out, using @elastic or Kibana are now actively business risks that your company needs to manage.

anonymoushash.vmbrasseur.com/2021/01/14/ela…
Read 4 tweets
14 Jan
And now a livetweet thread of a legal conference in the case of C21-31-BJR, Parler LLC v. @awscloud.
Parler suggests "AWS just has to flip a switch and Parler gets turned back on. Parler has been their customer for 2.5 years."
"They've met and conferred over some user content that violates not only Parler's user requirements, but also Amazon's." Yes, they'll do that, whether you want them to or not.
Read 29 tweets
14 Jan
This one grabbed my attention. I spent two years at @TaosTech. They’re the reason I moved to SF, started my own consulting firm, and met some wonderful people. It’s probably the best job I ever had.

Very savvy move by @ibmcloud.
I have a request to say more. Well okay!

The @TaosTech technical interview is a thing of genius. It's standardized, modeled after SAGE levels, and reshaped how I think about hiring engineers.
At the time my biggest gripe with Taos was that they didn't have a role into which I "fit." With the benefit of hindsight that's not their fault; I don't fit in anywhere, which is why I'm here.
Read 7 tweets
14 Jan
Let me point out some cloud magic tonight / say some nice things.

Normally I dunk on @awscloud in these threads, but today that puts me Nazi-adjacent. Plus AWS marketing's nerves are a little... frayed, so I fear for my safety.
The easy starting point is @awssupport. People are just rude as hell to them and they take it on the chin like the professionals they are. "Amazon is owned by a billionaire!" but he doesn't have to field the support tweets.

They also have to figure out when I'm trolling.
No matter how much you complain, they'll help you out. They're marvels, and good people too.
Read 16 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!