Hashicorp lays off 8% of staff
twitter.com
twitter.com
The day started. Everyone got an email saying what was happening and whether or not they were impacted. I was. I was given access to slack to say farewells for a few hours. I had a quick meeting with my senior manager. Then all access was cut and my personal email got all the needed details on what's next.
It sucked, but it was pretty humane.
But...
There was a leak two days before that it was coming. The dread of knowing you might be laid off is worse than being laid off. And everyone had it for 48 hours. It was brutal and the company ground to a halt.
I'm not mad at the leaker. They probably felt it was better that people know. But I don't think they were right.
I don't think telling investors about the layoff before the people being laid off is right. But I also don't think dragging it out for many days or weeks is healthy for anyone.
Issues I observed included:
* A complete lack of resourcing for the operational teams conducting the layoffs (talent, legal, etc)
* People receiving demands to sign their severance agreements within a few days.
* Severance agreements that were outright illegal in the regions of the employees there were laying off
* Severance agreements with wildly incorrect numbers
* Severance agreements that Shopify refused to honor after signing (to the point that it’s triggered a class action in Ontario)
* Poorly coordinated equipment return. Many of us have not received return boxes for our laptops over a month after the layoff. Some have received 3 or more boxes despite having no additional equipment.
* Questionably times layoff of all personnel in Berlin shortly before a works council was established. This has also resulted in an investigation by the local authorities.
Now I’ve been through my share of layoffs—they always suck and it’s reasonable to expect large ones will have problems. But this mantra that Shopify has done a good job of the May 2023 layoff or the previous layoff last year is a fallacy being pushed by an executive board at Shopify that has become increasing unaccountable for poor decisions and exercised even worse leadership.
I had only worked there for two months, so this brand new rather expensive laptop was turned into a paperweight for no reason other than to spite as far as I can tell. I still have it in my closet in case they decide we need to return it still (despite it being two years later). Anyways, if Cisco buys a company you're working for my advice is to immediately start looking for a new job.
Anybody ever manage equipment return programs? Are there compelling reasons to do this at scale that don’t boil down to data loss prevention.
In returning the equipment it actually protects the employee from compromise by creating a chain of custody for corporate data.
Sounds counterintuitive but it’s not. If the equipment needs to be destroyed — and it often is — it can be done properly.
People have no idea how easy it is to recover data from a single formatted drive.
Letting the former employee keep the laptop is the default, IMO. Although, frankly, I am not sure I would want to keep mine... sitting on a pile of a dozen laptops accumulated over the years.
And everyone watches porn on their on own devices anyway.
low power consumption and can probably run a couple of VMs, albeit not super well but well enough
Since I had no point of reference, with this being my first job, I asked a coworker if this was normal. He said no, all his friends with similar jobs at other companies were working like crazy.
That's when I knew this wouldn't last long. A few months later the company got sold for scraps to our largest competitor.
I learned then that it's better with a bit too much to do, rather than too little.
From a company perspective, it possibly makes less sense because you might prefer the oblivious folks to stay oblivious. But, personally, I'd prefer clear signals especially if it's not already blindingly obvious.
Messy layoffs may involve fewer people aware before the public announcement.
I’ve seen a number of terraform modules that try to use many small elements for things like AWS IAM permissions or Kubernetes configMaps, it helps document their individual purpose, it makes the output a bit cleaner sometimes, and until these pricing changes was basically just a style choice… now however it’s going to cost people more… I’d estimate at least a hundred (probably more) unnecessary resources are spread throughout the various custom modules and terraform registry modules in the last terraform repo I looked at… which adds up fast.
So moving forward I’d expect to see a slow trend towards features/fixes that function with more resources rather than less… Terraform has become somewhat legendary for its glacial pace of progress (go to GitHub, sort all the issues by thumbs up, have a read, see what gets closed what gets re-requested, what gets ignored with multiple pull requests) … this pricing change doesn’t fill me with confidence in the projects long term future… and neither does laying off staff at a company that already appears to be struggling to support its existing products while simultaneously trying to grow several new ones.
There’s no pricing based incentive structure for the type of sprawl you’re worried about. Not to say the trend you observed won’t continue. Just that if it does it’ll likely be due to composability or maintenance needs of the specific providers rather than juicing pricing.
I use a few third party providers and the quality difference is wildly variable, the update cadence is sporadic and unreliable on average, and not wanting to build scripts and tools is why maintaining my own terraform providers forked fro hashicorp isn’t really viable time wise either.
The point remains though: there’s no incentive system for the people who make the implementations decisions re resource granularity within providers to increase that because of this pricing change. For the most part they don’t work at HashiCorp. And even when they do, those abstractions are more often due to the underlying API they’re communicating with.
There is an incentive for project management on the AWS, GCE, Azure, Kubernetes, and the other Hashicorp maintained providers, to not prioritise work that reduces the number of potentially chargeable resources.
The first one I thought of was the time provider. It’s a virtual module like the null provider and all it does is put a logical delay into the dependency chain to handle edge cases… it would be all too easy to start assuming that customers use this module more in order to handle functionality that would require more code in other modules. They probably have metrics on resource and module use via terraform cloud (I don’t have the privacy policy and ToS memorised)
How strong the incentive is and if it’s ever really more than a subconscious influence on Hashicorp’s code the code that customers are more likely to use than 3rd party providers… is basically impossible to tell, but the inventive is absolutely there because Hashicorp’s pricing changes have made “number of resources in use by a terraform cloud customers” into a metric that the management will be looking at… the business development, the parts of the company that are responsible for making the money happen, will be measuring this number because it’s obviously important to them now…
And once you begin to measure something as a metric the incentive to game the metrics begins.
- HashiCorp employees directly maintain an astonishingly small number of those providers.
- For the most significant ones (e.g., AWS, Azure) they are working in some form of collaboration with the relevant vendors.
- The primary determination on what is broken out into a separate resource or not is based on the API said vendor exposes.
- For those major strategic providers I mentioned, they’ve been working to have the providers programmatically generated so it has little to no human intervention and increases the likelihood of day 1 support for any new service or features.
Incentives aside, there isn’t opportunity to affect things in the way you’re fearful of. The people with the biggest influence on the design of these things, and whether resources are consolidated or decomposed, work at AWS, Microsoft, Google, etc.
The problem is that, once you know what you are doing and understand the ecosystem, you can build a better experience using open source than they provide through TFC/TFE.
I wish I had a better idea for them…
I think Terraform has the same problem as Docker: HashiCorp isn't capturing the value of Terraform, and other companies are making more money off of it by seeing the real opportunity (like Docker/Docker Inc and Kubernetes). Cloud providers are reaping the benefits, and the other TACOS (Terraform Automation & Collaboration Software) like SpaceLift and Env0 see the value in bringing more collaboration and workflow aspects. There's nothing really "sexy" about automating and governing Terraform apply/plan.
I didn’t give them a dime and wouldn’t consider doing so in the future.
Terraform still needs bit of help when you want to run production grade:
state-locking (dynamodb) state-storing (s3) workspace/template management CI/CD functions (atlantis) secret management (vault)
and TFE gives you these right out of the box in a neatly packaged way. Of course, you can come up with different tools to meet those reqs (parenthesized above)
Terraform as a product is awesome and the azurerm backend plus azurestack provider is great. I hate Bicep and Terraform simplifies it all.
At every F500 or other large Enterprise I've been at you need to have some sort of support and escalation model. Lotta pushes to SaaS offerings too, esp. turnkey ones where it's their cloud and you pay an all-in price for software+infra+support.
I'd be paying but it's too expensive for what you get. Cost prohibitive for a small shop.
There's a huge prize for the company who delivers on how to build change management (windows, approvals, etc) into the IaC workflow.
https://ir.hashicorp.com/news-releases/news-release-details/...
- 1/31/2020: -56,217
- 1/31/2021: -84,009
- 1/31/2022: -289,314
- 1/31/2023: -297,287
This line seems to heading in a direction which is never making profit.
Nearly all of the tech IPOs over the last few years share the same story. These are companies that have never been shown to make a profit, with no clear model how to. Finally these companies need to prove this is possible.
We have an entire generation of C-levels running these sorts of companies that have never worked in a non-tech bubble where money is free.
Based on my own experience in a similar company, "leadership" has absolutely no clue how to make these things happen, but enthusiastically believes they will. Leadership earnestly believes that this about surviving a tough time, and soon everything will be back to low interest rates and free money.
I suspect these small layoffs will continue for a long time and then we'll start seeing more of these companies completely collapse.
Open source is involved in nearly every single aspect of the tech world and continues to dominate at an accelerating pace. Now, even commercial "AI" and even Robotics products seems like like they might also be in the crosshairs of the open source movement. This has happened in no time at all.
I've actually seen "spot" from Boston Dynamics clones which aren't as polished but would get the job done and what's incredible is, they're completely open source models and designs which people can start to manufacture from.
Sometimes I wonder if software and other areas of tech aren't far from becoming like other "boring" industries where there is a surplus of skills and workers and less demand. The days of the big money might be slowing down.
Let's see where it goes, but I completely agree with your statement about free money. It was easy to feel valuable and useful when money was free. Many people could be the CEO of a multi-million dollar start up. Now what's left is only those who actually have something to offer at an affordable price point. It will sort out the men from the boys.
They are growing and the cash burning each year is stabilizing. Isn't that the road to eventual profit?
There are a lot of legalities and practicalities around laying off people. It's one of those things that can get really expensive when it is not done properly. Telling people that they are being layed-off is pretty much the last step in that process. Companies don't actually have a lot of wiggle room here and have to plan for people lawyering up and pushing back.
I've been layed off myself by Nokia in 2012. It was a weird period for Nokia and there were many layoff rounds as the company was basically imploding. It sucks when that happens to you but I never took it personally.
I can't fault Nokia for the way they handled things and I never took it personally and look back on this as positive thing:
- They made me a nice financial offer based on years served.
- They offered plenty of support; including some startup funding. I ended up making use of that.
- Given what happened to the company afterwards, I'm not unhappy to not have been there for that wild ride.
Perhaps workers should change the structures of where they work with fractional ownership and a cut of the value they helped to create?
Employees should be singular as it’d be the type of resource. Each employee would have their own resource entry.
It’d be something like employees[id] repeated for each employee. Otherwise you’d be terminating everybody by targeting the entire collection.
Personally, I wouldn’t feel surprised if I were to get laid off tomorrow.
https://en.wikipedia.org/wiki/Vitality_curve
- Were there company-wide performance evaluations before the layoff?
- Was there a ~10% of promotions/bonuses at the same time?
If so, it was the MBAs and their horoscope driven management again.
> 1 click deploys + 3 cows included free. (Geese, ducks optional as add-ons)
https://www.hashicorp.com/resources/connecting-farms-and-gro...
https://www.hashicorp.com/blog/managing-applications-at-the-...