> The culture of Google is that you hire "the best" developers (say top 0.1%) and hamstring them with process and cumbersome tools so that you need 10x as many of them as another company would need and pay them 3x market rates, but it is OK because (1) at the scale they work at they can amortize the cost over a large user base and (2) they make monopoly products.
This describes basically every FAANG / MANGA company. Or even past that, any company that hit it big with a cash cow and now needs to come up with something new to satisfy shareholders.
In Meta's case, they have 3B MAU, they absolutely hire from the same tier of developers, and (pre-layoffs/economic downturn) they throw 10x more of them than they need at a problem. They even outcomp Google. The number of employees is more because employee growth was an indicator for company growth and only once that became a liability against the stock price it stopped.
Meta is just a newer company than Google.
> Facebook on the other hand, cares about internal DX, sees it a problem when developers are stuck with cumbersome processes, and greases the skids.
I am married to a Meta engineer and have mentored folks that have gone to work there. This might be the case if you work for a product that drives their cash cow of ads, but if you are doing anything that doesn't fit within that narrow bucket ... let's just say our viewpoints diverge significantly.
> The problem with React is that mediocre developers can use it to build big things that are too big for them to handle. The problem with Kubernetes is that above-average developers can use it to build small things they can't handle. And the scalability of Kube is more than almost all of the industry needs.
The problem with the Chrysler 300 is that bad drivers run over people. What does that say about the engineering culture at Chrysler?
Look, I agree that most cloud stuff is overkill, but I have a hard time indicting Google's entire engineering culture over a project they released into the wild 12 years ago that just happens to not fit your use case and that theoretical "above-average" developers wouldn't be able to tell that.
This describes basically every FAANG / MANGA company. Or even past that, any company that hit it big with a cash cow and now needs to come up with something new to satisfy shareholders.
In Meta's case, they have 3B MAU, they absolutely hire from the same tier of developers, and (pre-layoffs/economic downturn) they throw 10x more of them than they need at a problem. They even outcomp Google. The number of employees is more because employee growth was an indicator for company growth and only once that became a liability against the stock price it stopped.
Meta is just a newer company than Google.
> Facebook on the other hand, cares about internal DX, sees it a problem when developers are stuck with cumbersome processes, and greases the skids.
I am married to a Meta engineer and have mentored folks that have gone to work there. This might be the case if you work for a product that drives their cash cow of ads, but if you are doing anything that doesn't fit within that narrow bucket ... let's just say our viewpoints diverge significantly.
> The problem with React is that mediocre developers can use it to build big things that are too big for them to handle. The problem with Kubernetes is that above-average developers can use it to build small things they can't handle. And the scalability of Kube is more than almost all of the industry needs.
The problem with the Chrysler 300 is that bad drivers run over people. What does that say about the engineering culture at Chrysler?
Look, I agree that most cloud stuff is overkill, but I have a hard time indicting Google's entire engineering culture over a project they released into the wild 12 years ago that just happens to not fit your use case and that theoretical "above-average" developers wouldn't be able to tell that.