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.
Every company biases for something. @TaosTech biases for speed. If you have a project and need 4 engineers on the other side of the country next Monday who all know something esoteric and weird, Taos will find them and deliver them to you.

That's how they got me.
They're not perfect. At the time, they didn't see the value in my speaking at conferences, or in having community presence. That changed, but only seriously after I left. Before the Duckbill Group, Taos was my longest stint at one company.
But Taos's superpower was and is its people. My current colleagues @mike_julian and @jesse_derose worked there with me. That's how I met Jesse.
And I got to meet some amazing people. @GeorgeWHerbert and @Julie_Gund are the two that are active on Twitter, but an awful lot of folks in the DevOps space did a stint there. People joined, grew, and moved on. Then a lot of us became clients.

• • •

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

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
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
13 Jan
I read this tweet aloud to my wife.

@bequinning: “Oh, Ambika?! We went to law school together!”
I always wondered how an attorney would frame "cool story, bro" and now I know.
I'm starting to think that maybe the Parler folks might not fully grasp how complicated web properties work.
Read 5 tweets
13 Jan
In this thread (which you may want to mute), give me a company and I'll tell you why they fired me.

I'll start with @F5: because I used the word "refreshing" in their marketing copy.
I felt sorry for the princess our customers had to kidnap for ransom to pay for our product, so I bought her a taser.

I violated their ethics policy by having some.

Read 73 tweets
12 Jan
There's been a lot of noise lately about follower counts, so I'm pleased to leap into that and take a remarkably petty victory lap:

I now have more followers than the hardest working account in cloud, @AWSSupport.
Their milquetoast advice will work, but my terrible advice is way better!
@AWSSupport: "Use RDS as your database!"
Me: "Use Route 53 as your database!"
AWS: "Lock down your S3 buckets to avoid data leaks."
Me: "Save money by storing data in other people's insecure S3 buckets."
Read 5 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!