The Michelin kitchen metaphor
Definition: lauren-tan’s reframe of the buzzword “software factory” as a Michelin-starred kitchen, chosen because a kitchen carries craft and quality where a factory connotes throughput. She introduces it in 2026-10-05-youtube-poteto-software-factory:
[11:20] “I’ve never really liked the term software factory. Not because it’s not accurate, but a lot of people, when they think factory, don’t equate that with quality or craft, which are very important to me. Michelin Kitchen is the thing I’ve landed on. It’s much more aspirational.”
The name fits a person whose handle is potato and who likes cooking.
The home-cook thought experiment
The metaphor is really about scaling (12:48). As a home cook you are a one-person show, cutting every vegetable and doing every bit of prep and cleanup. Add your family to the kitchen and “most people would get very stressed, so many people moving around in my kitchen, they have no idea where the utensils are.” The host jokes his capacity is one person. The useful question is not whether more bodies help, but how to divide the work “in a way that actually makes the sum better than the total of its parts” (13:50).
The chef is the tech lead
Once you are a chef you stop cooking every dish (14:08): “You’re almost like the tech lead for the kitchen, or the CEO of the kitchen. You have to think about when do you order ingredients, how do you store and prepare them, when they have to be ready. It’s a whole job that is not just cooking.” This mirrors the engineer who no longer writes the code but stays responsible for the outcome, and whose reputation is still attached to it (14:49). The thing you actually build, in her words, is the kitchen itself: your skills, your environment, your codebase are “the new ingredients.” See environment-and-constraints.
Open chain restaurants
The scaling claim in one line (34:02): “I’ve spent the time building one kitchen and one restaurant, and now I don’t actually have to be there anymore.” She treats each big project as a restaurant and helicopters between several. The host extends it (40:10): manually starting every chat is carrying orders to the chefs yourself, whereas an agent running the pass does the expo for you. This is the same idea as the trust-ladder-agents capstone, and as the coordinator-agent pattern in inner-outer-loop-agents.
Sampling, and the dimmer switch
Tasting is how quality stays real without a bottleneck (49:34): “You don’t want to be in a position where you’re not tasting your food ever again, but for scale you cannot be tasting every single dish, especially with multiple restaurants. It becomes about sampling.” Here, she concedes, the factory image is the better one (50:01): a quality supervisor on a line samples rather than inspects every item. The host closes the loop on “dark factory” (54:49): her method is not Karpathy’s original vibe coding where you forget the code exists, so think of a dimmer switch, some parts dark and some light. The kitchen beats the factory on that point. Even a restaurateur drops in to taste. See verifiability-and-one-way-doors for what has to be true before you can let the line run dark.
Related
- trust-ladder-agents: the ladder the kitchen is a picture of
- environment-and-constraints: what the chef actually builds
- inner-outer-loop-agents: the pass, the expo, and the orders
- agent-verification-skill: tasting, at scale, as sampling