优化软件工厂
Optimizing Software Factories
软件工程团队中AI与人力比例的选择核心在于韧性而非吞吐量。在10/90比例下，约20名工程师使用Copilot等AI工具，保持传统层级结构；50/50比例时，12名工程师管理代理群，角色转向解决方案架构；90/10比例则仅需3名工程师核心操控自主代理，负责生成、测试和部署，无管理层级。高AI比例虽提升效率，但知识集中于少数人，团队利用率达100%，一旦人员离职将引发严重风险。借鉴制造业70-90%利用率原则，保持冗余可增强系统稳健性。因此，目前大多数初创公司不宜过度依赖AI。
Tomer Tunguz 把 AI 团队比作工厂，点出反直觉结论，AI Agent 不是越多越好，关键在于预留弹性，避免单点故障。做工程管理的读完会重新算一算配比。
In short : A framework for thinking through three future states of engineering spend: 10% AI / 90% labor, 50/50, and 90% AI / 10% labor. Each ratio implies a radically different org chart, risk profile, and profitability trajectory. The post argues that most startups should not overoptimize toward the 90/10 extreme because the key-person risk and institutional fragility are not yet priced into the model.
What happens when a startup employee leaves on a Monday?
In a twenty-person engineering team, one resignation is a 5% headcount loss. The remaining nineteen absorb the work.
In an AI-pilled three-person team running twenty autonomous agents, one resignation is a 33% headcount loss.
The agents do not resign. They keep generating, reviewing, testing, and deploying. But one-third of the institutional memory that trains, prompts, validates, and debugs the agent fleet walks out the door.
The tradeoff at the heart of AI/labor ratio decisions is not throughput. It is resiliency.
At 10/90 (10% AI, 90% labor), a typical mid-stage startup engineering budget powers ~20 engineers and a layer of Copilot, Cursor, and inference spend. Traditional hierarchy. Human code review as the bottleneck. The org chart looks familiar.
At 50/50, the same budget powers ~12 engineers and a fleet of agents. Engineers become solution architects, problem decomposers, and prompt designers. Manager span of control widens because agents do not need standups.
At 90/10, three engineers sit at the center of a constellation of autonomous agents that generate, review, test, deploy, monitor, and optimize. No managers. No hierarchy. No redundancy.
If we are building software factories, maybe it’s time to study operations research.
In manufacturing, the rule of thumb is simple: run your factory at 70–90% utilization. At 100%, one breakdown cascades into missed deadlines, burned teams, and lost customers. The slack is not waste. It is the feature that keeps the system robust.
Engineering teams are not factories, but the same logic applies. When you concentrate orchestration knowledge in three heads, you are running at 100% utilization.
Most startups should not make that bet yet.
来源：Tomer Tunguz 博客（VC 分析） · tomtunguz.com