When Private Equity boards attempt to capture AI returns, a common line item targeted is engineering headcount. In Episode 16, Paul and Dave analyze a recent LeadDev report detailing Meta’s attempt to shrink engineering teams around AI agents. While Meta saw a staggering 220% increase in code commits, only 36% made it into production, while technical incidents jumped 40% and time spent firefighting production outages exploded by 70%.

Corroborated by broad industry data from DX showing a precipitous drop in Developer Experience (DevEx) scores, Dave and Paul break down why "token-maxing" without human system ownership creates massive P&L liabilities. This episode outlines why "two-pizza teams" (5 to 8 engineers) remain the optimal operational unit, why replacing developers with agents starves your system of critical operational memory, and how outage firefighting actively destroys EBITDA.

Key Takeaways:

• The 220% vs. 36% Gap: Meta's internal experiment proved that generating code volume with AI agents does not translate to revenue-generating features. Commits skyrocketed 220%, but actual production shipping only grew 36%.

• The 70% Firefighting Tax: Replacing developer oversight with autonomous agents caused technical incidents to spike 40% and developer firefighting time to surge 70%. Every hour spent firefighting outages in production is paid labor lost to reactive crisis management rather than value creation.

• System Ownership Cannot Be Outsourced: You cannot outsource the operational responsibility of running a company to AI models trained on generic public code. When complex production systems break, human engineers who understand the architecture must be available to fix them.

• The Return of the Two-Pizza Team: Meta’s research concluded that the ideal team size remains 5 to 8 engineers. Shrinking teams below this threshold creates severe on-call burnout, rotation failures, and institutional risk.

https://leaddev.com/ai/meta-tried-to-shrink-engineering-teams-around-ai