It’s also potentially dangerous. “Your résumé seems awfully familiar somehow but we’ve never met and I don’t remember your name. You must have stolen it from somewhere…”
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.
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.)
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.
As @vmbrasseur points out, using @elastic or Kibana are now actively business risks that your company needs to manage.
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.
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.
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.