|
|
|
|
|
by rdiddly
481 days ago
|
|
They clearly don't mean one person with AI now vs. 100 people with AI now. They're comparing one person with AI now to 100 people without AI before. Regardless, one person still costs 1/100 as much as 100 people. Let's say each of the 100 adopts AI and multiplies their productivity by 100. Does their company need its total engineering productivity multiplied by 100? They might settle for let's say 3X and save 97% of the costs by firing 97 people. (I tend to ignore most of the hype and I'm dubious about that 100X figure, but I'm taking it at face value here for illustrative purposes.) |
|
In 2018, I wrote about scaling big while staying small using serverless computing (https://cloud.google.com/blog/products/gcp/scale-big-while-s...). But by 2020, instead of leaner teams, we saw more hiring and even bigger orgs—ironically, even at companies selling serverless services.
Why? Because incentives at large companies favor empire-building (prestige from managing big teams) over efficiency. I expect the same inertia with AI: solo devs will fully embrace AI, serverless, and freemium to race ahead, while big teams will adopt AI at a crawl.