Software Engineering Is Becoming Factory Engineering — Zach Lloyd, Warp
- Source
- youtube.com
- Author
- AI Engineer
- Date
Context
A software factory, in Warp's account, is a workflow that carries incoming work through triage, product and technical specs, implementation, review, verification and monitoring. The proposal expands automation beyond producing a code change to organizing the work around it.
That changes the engineering task being described. Someone must decide how requests enter the process, what evidence makes a change acceptable and how problems discovered after release feed into further work. Warp's founder, Zach Lloyd, predicts that every serious project will run such a factory, much as projects now have CI/CD. The prediction is broader than the workflow presented, but the workflow explains what engineers would need to build and maintain.
- Lloyd, who led engineering on Google Docs, says he still ships constantly but has not written a line of code in six months.
- His argument for open-sourcing Warp after five years closed: when software is cheap to build and clone, a great product is not enough, and building in the open creates an ecosystem around it.
- He says automation now absorbs the usual cost of running in the open, handling noisy issues and sloppy pull requests that once made open source painful to maintain.
- His factory stages run from inputs and triage through product and tech specs, implementation, review, verification and monitoring, on top of a shared architecture and data layer.
videoRethinking Claude Code Best Practices — Lydia Hallie, Anthropic
videoStop Shipping LLM Settings That Only Win on Paper - Rohan Pandey & Balaji Varadarajan, DigitalOcean
videoYour SKILL.md Is 70% Stuff the Model Already Knows - Nikolay Petrov, Intel
videoYour Spec Has Bugs. Catch Them Before Your Agent Codes. - Rajath Mahendrappa Kotyal, AWS
Checking sign-in…
Loading comments…


