Warp Founder Zach Lloyd: Software Engineering Is Becoming Factory Engineering
Zach Lloyd, founder of Warp and former principal engineer who led engineering on Google Docs, argued at the 2026 AI Engineer World’s Fair that software engineering is turning into factory engineering. Engineers will build and manage systems that execute development steps rather than writing code themselves. He connected this thesis to Warp’s open-source business logic, described the factory’s closed-loop and skill self-improvement loops, acknowledged the mechanization risks of the factory metaphor, and emphasized that human product judgment remains irreplaceable.
Zach Lloyd, founder of Warp and a former principal engineer who led engineering on Google Docs, made this argument at the 2026 AI Engineer World’s Fair: software engineering is becoming factory engineering. His own experience serves as the starting point for this thesis—despite being the founder of Warp and having previously led engineering at Google Docs, he still ships products frequently but has not written a single line of code in the past six months. The factory he describes operates as a closed loop: ideas enter the system, agents perform triage, complex tasks generate product specifications and technical specifications, humans review the specifications, agents implement the code, both agents and humans conduct reviews, agents verify the output, humans review the final product, it is shipped, monitored, and observed results are fed back into the input stream. The engineer’s role shifts from writing code to building and managing the system that executes these steps.
Lloyd connects his factory thesis to the business logic behind Warp’s decision to open source its project. His reasoning is that when building software becomes cheap, cloning it also becomes cheap, making it difficult to establish a moat based solely on the product itself. Advantages such as distribution, ecosystem, community, brand, data, and capital lie outside the product, yet startups typically lack these resources. While open source can cultivate an ecosystem and community, the traditional maintenance burden—noisy issues, sloppy pull requests, and lengthy code reviews—has historically made this path unrealistic for resource-constrained teams. Lloyd stated that automation changed Warp’s calculus: they built an entire suite of automations around their open-source project, making the public factory both a development system and a mechanism for handling contributions.