When Output Is Cheap, Taste Is Everything
There’s a tweet making the rounds from Nat Eliason that nails something I’ve been feeling for months: “Nearly every ambitious person I know who has dived into AI is working harder than ever, and longer hours than ever.” He adds that he’s never worked this hard, or had this much fun.
I get it. I really do. But let’s sit with that observation for a moment, because there’s something hiding inside it that most people are glossing over.
The intoxication of infinite output
For the first time in most of our careers, our tools can genuinely keep pace with our imagination. That’s an extraordinary shift. If you’ve spent years bottlenecked by implementation (writing boilerplate, configuring pipelines, wrestling with CSS that refuses to centre a div), the sudden removal of that friction is intoxicating.
You think it, you describe it, and something usable appears. Of course you’re going to work longer hours. The feedback loop that used to take days now takes minutes. It’s like someone handed you a fire hose and said: “go build.”
And so we build. And build. And build some more.
Here’s where I want to pump the brakes. Not on AI itself, but on the assumption that more output automatically equals more progress.
Speed without direction is just velocity
When the cost of producing something approaches zero, the bottleneck shifts. It moves away from can we build this? toward should we build this? That’s a fundamentally different question, and it requires a fundamentally different skill set.
I’ve seen it so many times in the composable tech space: teams adopt shiny new tools, ship features at breakneck speed, and end up with a bloated product that solves problems nobody actually has. The tools weren’t the issue. The lack of a clear destination was.
AI amplifies this pattern. It doesn’t just let you build faster; it lets you build wrong faster. And the fun of building, that dopamine hit of seeing things materialise, can mask the fact that you’re sprinting in circles.
The case for taste
If output is cheap, what becomes expensive? Taste. The ability to look at ten possible directions and choose the one that actually matters. The instinct to say “no” to nine good ideas because one great one deserves your full attention.
Taste isn’t some abstract aesthetic sensibility. In practice, it’s a combination of domain expertise, user empathy, and the hard-won judgment that comes from having shipped things that failed. AI can’t give you that. It can generate options all day long, but it can’t tell you which option your users will love, which one aligns with your strategy, or which one you’ll regret building six months from now.
In other words: AI is an incredible how engine. But what and why remain profoundly human questions.
The rest nobody wants to talk about
There’s another dimension to Eliason’s observation that gets conveniently ignored. If ambitious people are working harder and longer than ever, that trajectory has a ceiling. And it’s not a productivity ceiling. It’s a human one.
The most valuable insights I’ve had in my career didn’t come while staring at a screen. They came in the shower, on a walk, or halfway through a conversation that had nothing to do with work. Rest isn’t the absence of productivity. It’s the condition that makes taste possible.
When you’re exhausted and hyperstimulated from twelve hours of AI-assisted building, your judgment deteriorates. You start shipping because you can, not because you should. The quality of your decisions, the very thing that differentiates you in an age of abundant output, degrades precisely when you need it most.
Simply put: if your competitive advantage is taste, and taste requires a rested mind, then rest is a strategic investment.
The real flex
I’m not arguing against enthusiasm. The energy around AI right now is earned. Building with these tools is genuinely exhilarating, and the people leaning in are going to shape what comes next.
But the people who will shape it best aren’t the ones who work the most hours. They’re the ones who pair relentless curiosity with the discipline to step back. The ones who use AI to explore ten directions in an afternoon, then sleep on it before committing to one.
The real flex in 2026 isn’t how much you can produce. It’s the restraint to produce only what matters.
When output is cheap, your greatest leverage isn’t how much you build. It’s the taste to know what’s worth building, and the rest required to see the difference.
On this page
Related articles
The biggest risk to AI is the enterprise org chart
This article argues that the real risk of corporate AI is not rogue superintelligence but how large organizations deploy it, usually in service of cost-cutting rather than creating new value. Big enterprises buy AI like office furniture, wrapped in committees, procurement, and risk matrices, so it ends up optimizing ticket deflection and headcount instead of enabling innovation. The real bottleneck is bureaucracy, not intelligence. In contrast, a roughly 500-person company has enough depth to build serious systems but short enough communication paths that the person with the problem can help build the solution. AI lets domain experts prototype directly, shortening the loop between friction and fix. The key is governance that enables safe experimentation instead of vetoing it, using AI to expand reach rather than just reduce costs.
- Composable architecture
- AI engineering
- Frontend
Intuition and the real cost of research
This article explores how AI changes the balance between research-heavy processes and intuition-driven building, especially in product and technical work. The author reflects on a career of moving faster than surrounding teams, where strong intuition (really compressed experience from shipping many similar things) often clashed with expectations for lengthy research and documentation. As AI makes implementation and iteration dramatically cheaper and faster, the true bottleneck shifts from building to deciding what is worth building. Research still matters for those without established mental models, and for environments where stakeholders need evidence and paper trails. But when iteration costs hours instead of weeks, over-indexing on analysis can become the real drag. The piece argues that, in an AI-enabled world, experienced intuition is not anti-process; for the right people and problems, it is the process.
- Composable architecture
- AI engineering
- Frontend
TDD finally makes sense
AI coding tools have removed the old excuse that test driven development is too slow or too costly. When AI can generate both implementation and test scaffolding in minutes, the time cost of writing tests first collapses, turning TDD into an obvious quality and productivity win. The real risk now is vibe coding, where developers ship AI generated code that looks fine but crumbles under real edge cases. By using AI for planning, then encoding that thinking as tests and letting the AI implement against them, teams get faster feedback, more reliable code, and fewer hotfixes. In an AI assisted world, the competitive advantage shifts to defining behavior and edge cases up front, and TDD becomes the discipline that makes that thinking explicit.
- Composable architecture
- AI engineering
- Frontend