The Greenhouse and the Lens: Two Modes of Agentic AI Work Aug 01, 2026 Software Engineering AI The Greenhouse and the Lens: Two Modes of Agentic AI Work A greenhouse and a lens both run on sunlight,
By Coderz Club · 2026-08-02 · Tags: ai
The Greenhouse and the Lens: Two Modes of Agentic AI Work
Aug 01, 2026 Software Engineering AI The Greenhouse and the Lens: Two Modes of Agentic AI Work A greenhouse and a lens both run on sunlight, and they do opposite things with it. The greenhouse traps ambient heat and holds it, so everything inside grows a little faster than it would outside: flowers, herbs, weeds, whatever happens to be in the soil. The lens takes the same light and concentrates it on a single point until that point catches fire. One gathers energy and lets everything grow at once, diffuse and a little chaotic. The other is a discrete event you engineer: aim, focus, hold steady, ignition. At first, I thought the two modes mapped cleanly onto software engineering experience: the junior engineer lives in the greenhouse, growing weeds and flowers indiscriminately, while the senior engineer aims a lens at one well-defined spot at a time. But when I applied the metaphor to my own work, the mapping fell apart. Neither mode is the advanced one. They’re distinct tools for distinct jobs, and much of the frustration I see with agentic AI comes from running one mode when the work demands the other. Greenhouse mode is for when you don’t yet know what you want. My AxiDraw plotter experiments are pure greenhouse: I’ve had Claude Code generate dozens of tools for making plottable art. Most of the results were mediocre, a few were delightful, but none of them were really planned. I just played and evaluated the results afterwards. The same was true for a small macOS/SwiftUI app I made (well, Claude made) that converts Markdown to Word documents. There was never a spec, a design, or a plan. I asked Claude to build a tool that had an audience of one and a shelf life of maybe a week. These tools came about because the cost of trying things out has dropped to nearly zero. I wrote about a version of this when I said Claude Code is unreasonably good at building MVPs: build a tool or a toy, see if it’s useful or fun, and go from there. Lens mode is the opposite discipline. You know exactly what done looks like, and you concentrate everything on getting there. The agent proposes ten things and you discard nine because they aren’t on the line between here and done. When people talk about the shocking power of agentic AI tools, this is usually the mode they mean, but it’s worth being precise about what that power is: leverage on a known target. Both a lens and the most powerful generative AI model in the world can be useless when you don’t know where to point it. Picking the target—and focusing on it—is your job. Furthermore, I’d argue that the really advanced skill is knowing which mode the work in front of you requires, recognizing which mode you’re currently in, and understanding how to shift yourself to the correct mode when drift has occurred. For instance, I sit down to ship a specific feature, obvious lens work, and forty minutes later Claude Code is scaffolding an admin panel I never asked for. And I nod along, because watching things grow feels like progress. It runs the other direction too: I set out to explore and end up polishing one half-formed idea to production quality, because finishing is comfortable and wandering isn’t. In both cases the failure is the same: I lost track of which mode I was in. In May I argued that domain expertise has always been the real moat: the scarce asset in an agentic world is a verified mental model of the domain, like an oracle that tells a right answer from a plausible wrong one. That same oracle works here, too. In the greenhouse, the oracle sifts through the thousand sprouting plants to find the three worth keeping. With a lens, it rejects the plausible-but-wrong output that would pull you off the line between here and done. And it’s the oracle that notices drift: you can only feel yourself wandering off target if you hold the target in your head. So, as your work progresses and you start to get into your flow, do a gut-check: greenhouse or lens? They’re both legitimate and productive approaches in the right circumstance, but expertise means cultivating the sense of which to apply and when.
Aug 01, 2026 Software Engineering AI The Greenhouse and the Lens: Two Modes of Agentic AI Work A greenhouse and a lens both run on sunlight, and they do opposite things with it. The greenhouse traps ambient heat and holds it, so everything inside grows a little faster than it would outside: flowers, herbs, weeds, whatever happens to be in the soil. The lens takes the same light and concentrates it on a single point until that point catches fire. One gathers energy and lets everything grow at once, diffuse and a little chaotic. The other is a discrete event you engineer: aim, focus, hold steady, ignition. At first, I thought the two modes mapped cleanly onto software engineering experience: the junior engineer lives in the greenhouse, growing weeds and flowers indiscriminately, while the senior engineer aims a lens at one well-defined spot at a time. But when I applied the metaphor to my own work, the mapping fell apart. Neither mode is the advanced one. They’re distinct tools for distinct jobs, and much of the frustration I see with agentic AI comes from running one mode when the work demands the other. Greenhouse mode is for when you don’t yet know what you want. My AxiDraw plotter experiments are pure greenhouse: I’ve had Claude Code generate dozens of tools for making plottable art. Most of the results were mediocre, a few were delightful, but none of them were really planned. I just played and evaluated the results afterwards. The same was true for a small macOS/SwiftUI app I made (well, Claude made) that converts Markdown to Word documents. There was never a spec, a design, or a plan. I asked Claude to build a tool that had an audience of one and a shelf life of maybe a week. These tools came about because the cost of trying things out has dropped to nearly zero. I wrote about a version of this when I said Claude Code is unreasonably good at building MVPs: build a tool or a toy, see if it’s useful or fun, and go from there. Lens mode is the opposite discipline. You know exactly what done looks like, and you concentrate everything on getting there. The agent proposes ten things and you discard nine because they aren’t on the line between here and done. When people talk about the shocking power of agentic AI tools, this is usually the mode they mean, but it’s worth being precise about what that power is: leverage on a known target. Both a lens and the most powerful generative AI model in the world can be useless when you don’t know where to point it. Picking the target—and focusing on it—is your job. Furthermore, I’d argue that the really advanced skill is knowing which mode the work in front of you requires, recognizing which mode you’re currently in, and understanding how to shift yourself to the correct mode when drift has occurred. For instance, I sit down to ship a specific feature, obvious lens work, and forty minutes later Claude Code is scaffolding an admin panel I never asked for. And I nod along, because watching things grow feels like progress. It runs the other direction too: I set out to explore and end up polishing one half-formed idea to production quality, because finishing is comfortable and wandering isn’t. In both cases the failure is the same: I lost track of which mode I was in. In May I argued that domain expertise has always been the real moat: the scarce asset in an agentic world is a verified mental model of the domain, like an oracle that tells a right answer from a plausible wrong one. That same oracle works here, too. In the greenhouse, the oracle sifts through the thousand sprouting plants to find the three worth keeping. With a lens, it rejects the plausible-but-wrong output that would pull you off the line between here and done. And it’s the oracle that notices drift: you can only feel yourself wandering off target if you hold the target in your head. So, as your work progresses and you start to get into your flow, do a gut-check: greenhouse or lens? They’re both legitimate and productive approaches in the right circumstance, but expertise means cultivating the sense of which to apply and when.