Meta tried to shrink engineering teams around AI

13 pointsposted 5 hours ago
by mooreds
(leaddev.com)

6 Comments

bhouston

3 hours ago

I think that Meta was just too early.

I think that software team size per product (how ever you define that) are going to continue to shrink over the next 3 years. You will only need a single product designer/developer/manager per small product eventually.

That said, we will ship a lot more products that will partially make up for that per-product team size shrinkage.

Taronar

35 minutes ago

I Mean if ai was ready to automate the workforce it would have been done already, logically and statistically speaking the first few people are bound to fail before the penultimate front runners will be the real winners.

Ancalagon

3 hours ago

They won’t even need managers, just watch.

chopete3

4 hours ago

If there is 36% increase in features shipped with half the team - that is a win.

Even if the new (half) team produces the same number of features it is a win.

Why is PR count or number of issues relevant for the overall outcome?. The article is trying to force fit the point their point about AI effectiveness

oenton

6 minutes ago

> Why is PR count or number of issues relevant for the overall outcome?

Agree on PR count but how is number of issues not relevant? If throughout increases 36% but incidents also rise by 40% that’s pretty clearly a net negative IMO.

joshAg

4 hours ago

Likewise, major technical and security incidents increasing 40% is a loss, and the amount of time employees spent firefighting them rising 70% is a loss.