“ As hard as this is for all of us, our future is bright. I look forward to working with you to propel Elastic into that future as we make Elastic a generational brand”, especially since he earlier says those being laid off may not even know that for up to 24 hours.
Nobody wants to be told they have been laid off by finding your name in a power point in the morning, just because you live in a different time zone. They have offices around the world, so it is difficult to inform everyone at the same time without calling someone in the middle of the night.
At the same time those who have been informed are talking to other employees, and news spread fast. So they end up with a compromise - inform the company about the process.
They are handling it better than what I experienced not long ago. After announcing the layoffs and informing the affected, they did not communicate who was affected until the week after. Colleagues who had a good network knew who were affected by talking to each other, while others were left in the dark
1: https://grafana.com/blog/2022/07/29/inside-grafana-labs-my-f...
Come join the Oracult
Snowflake ... well let's not go there.
Signed: a Brickster
Layoff expensive workers to hire cheaper ones.
It's right there at the top, very prominently.
One bizarre side-effect of these layoff announcements is learning all the cringe-worthy names these companies have for their employees. Elasticicans? Tweeps? Stripes? I'm guessing this is a SV thing? Do these infantilizing names actually do anything to build company culture?
What has Google really done that wasn't first done by the Yahoo!s at Yahoo!?
Does no-one plan beyond the next quarter anymore?
How much more Elastic wanted than AWS, didn't make sense, not even factoring support and hosting. It was like almost twice as much.
Morally, I get why I should have gone with Elastic. Too bad businesses aren't about morals.
One thing is that the "mainstream" ELK develops at a much faster speed than the OpenSearch fork, and a lot of the nice features in new versions are nowhere to be seen in OpenSearch.
The cynic in me is telling me this is all planned by big tech and government. Heck, Zuckerberg waited to fire his staff a day after the midterms were done. This is no coincidence.
It's disappointing. Elastic had it. Unforced errors abound.
Pretty much everything MongoDB did right, Elastic did the opposite and failed. Instead of being the best place to run Elasticsearch, one of the most popular open source projects ever, they blew all that brand equity on a series of mediocre solutions that were outcompeted.
One thing about Elastic is that their roots are in on-prem / self-managed software and selling support to enterprise customers. This led to our cloud strategy being based around ECE (Elastic Cloud Enterprise), with the idea we would eventually fully unify this on-prem version of our Cloud product with our actual SaaS, and just run ECE "at scale". During that time we got stuck in the slower Elasticsearch "quarterly minor + monthly patch" release cycle (SaaS did have a shorter one but it was also troubled) and spent countless engineering effort troubleshooting enterprise customer's own infrastructure (imagine stuff like "ohhh, I see, you V-Motioned a server hosting ZooKeeper containers, and you're running on spinning disks" after 2 weeks+ of back and forth). We couldn't easily add table-stakes features to our SaaS because we needed it to run on-prem too, even though ECE is very limited in the types of supporting infrastructure we could add (basically just ZooKeeper and Elasticsearch). I think they are trying to move past this strategy and onto a SaaS-only K8s based approach but I fear too much time was squandered. I hope I'm proven wrong.
https://www.aboutamazon.com/news/company-news/a-note-from-ce...
Not even totally COVID or Russia’s fault either… stock prices really bubbled since 2008, with many companies trading well above a level that there is any rational justification for.
