Meta laying off 10% of staff when revenue is at an all-time high, revenue growth is a beast (33% YoY!!), profits at an all-time high:
just depressing
These layoffs are not because Meta needs to lay off, but because Zuck wanted to lay off for whatever reason
Meta reached to interview me for a principal role the same week they decided to layoff 8,000 people!
I’m sure there was at least 1 out of those 8,000 people who got let go who would’ve been a good fit for the role they wanted to hire me for. A few of my staff engineer friends got let go so I know this is true.
Instead they:
- axe everybody
- treat them like a cost
- rehire where there’s pain
What ever happened to employee retention?
Why do companies expect us to be loyal to them if they don’t even try to retain us when they have hundreds of billions of dollars?
It would be cheaper financially for them to retain one of those 8,000 people. It would be cheaper emotionally for the people who got let go too
How do these big tech companies expect people to put their blood, sweat and tears into work while also saying, “yeah we’ll cut you at any moment.”
I don’t know. The culture around AI and layoffs has gotten unbelievably toxic
It’s 2018 and your coworker just sent you a 400 line pull request.
You get a cup of coffee and sit down to review it.
It’s beautiful. Elegant micro-refactors. Crispy method names.
You catch a few things, but that’s ok. It’s part of the dance. They didn’t consider extensibility on part of their API. Here’s a comment buddy.
They respond in an hour saying they think we should do one piece differently than your comment. Hey let’s jump into a room and figure it out. We can’t just agree to disagree, this code is too important.
The PR merges and goes to prod. You feel a shared sense of ownership and accomplishment.
That night you go to sleep and dream of that code. You can still see the shapes of it on the backs of your eyelids, your IDE syntax highlighting sparking neurons in your reptile brain.
You go to work the next day ready to go. You understand the system. N is your foundation. Time to build n+1.
We experienced an outage at Coinbase last night, which is never acceptable. The root cause was a room overheating in an AWS datacenter when multiple chillers failed. We design our services to be redundant to downtime in any one AWS Availability Zone (AZ), and most of our systems worked this way last night, but not all.
Our centralized exchange did not. Exchanges have unique architectures that optimize for latency and co-location of clients. It is possible to make exchanges resistant to AZ failures, but this can introduce latency delays that are not desirable along with breaking customer co-location. Given this incident, we'll revisit these tradeoffs to ensure we're giving you the best possible venue to trade. At a minimum, the duration of an outage should be able to be reduced considerably when an AZ move is needed.
Thank you to the AWS and Coinbase teams for working through the night to mitigate the issue. We’ll share the detailed technical summary once it's ready.
Today is a hard day. I shared this note with the @linear team today: We’ve made the difficult decision to increase our workforce. This is not a cost-cutting exercise or a reflection of anyone’s performance. We’re simply reimagining every role for the agentic AI era. We’re hiring. We’re sorry about that.
Pretty sure this is what @brian_armstrong means when he says, “Non-technical teams are now shipping production code and many of our workflows are being automated.” Keep up that good workflow @coinbase 🫡
Everybody is adding a feature where you can manage your agents from your phone. Don't use it. You'll just get even more addicted, and will burn out even quicker.
Best career advice i ever got:
Find a lowkey 9-5 that has the LEAST amount of responsibility. Use the extra time to start a side hustle and scale your business from there.
This strategy has helped me become financially free.