#501 – DHH: Future of Programming, AI, Agentic Engineering, Vibe Coding & Linux
- 01The Agentic Revolution Has a Precise Timestamp
- 02The Three Distinct Phases of the Agentic Era
- 03The Real Bottleneck Is Human Bureaucracy, Not Implementation
- 04Over-Specification Is Now Actively Harmful to Agent Output
- 05The Programmer's Advantage Is Diminishing
- 06Parallel Multi-Machine Agentic Setups Are the New Productivity Architecture
1. Key Themes
The Agentic Revolution Has a Precise Timestamp
DHH identifies November 24, 2025 as the exact inflection point when AI shifted from autocomplete tool to genuine agent capable of producing production-quality code. The quality jump was not just raw intelligence but the ability to use tools, check its own work, and operate autonomously within a codebase.
"Then we get to November 24th, 2025. Opus 4.5, to me, was the dividing line. Where suddenly, I didn't even try it on the 24th. I think I tried it on the 26th. I give it a couple of tasks. And I realized that the quality of the output is uncannily close to what I would have written." 00:13:23
The Three Distinct Phases of the Agentic Era
DHH breaks down the agentic era into three distinct moments, not one: (1) single-agent driving November–February where you direct every step; (2) subagents and parallel execution from early spring; and (3) the current summer phase where the agent designs the solution and humans just approve.
"Finally now, this summer, with Opus 5, Fable, and Sol, GPT Sol, and to a lesser extent, some of the open weight models, we've arrived at a new era where I'm not telling it where we're going. I'm telling it the problem I have. I'm telling it the fuzzy, vague idea I have. It tells me where we're going. It tells me which path to take." 00:17:11
The Real Bottleneck Is Human Bureaucracy, Not Implementation
DHH argues that large organizations are not seeing AI-driven acceleration because the bottleneck was never code-writing — it was human communication layers, approval chains, and the absence of vision and taste. Giving more implementation speed to a vision-less organization just ships bad ideas faster.
"As soon as you're having human teams work together on something, the bottleneck is rarely implementation. It's human bandwidth and communication... The revelation I've had working on Amachi the last three months is that to get that magical 10x, 100x, in a few rare cases, 1000x productivity boost, you have to interact with the agents directly. And you cannot intermediate that bandwidth with another human because it's simply too slow." 00:24:43
Over-Specification Is Now Actively Harmful to Agent Output
DHH reveals that Anthropic's own system prompt for Opus 5 shrank by 80% because overly prescriptive human instruction was degrading output quality. The skill to develop now is restraint — giving high-level problems, not prescribed solutions.
"Opus 5 was that the system prompt that they shipped for Opus 5 and presumably also Fable shrunk by 80% because the agent not only needed far less human instruction, it was actually being damaged by overly prescriptive humans." 01:02:26
The Programmer's Advantage Is Diminishing — and Sometimes Reverses
DHH makes the counterintuitive admission that being a highly experienced programmer was actually a liability in the second agentic moment, because programmers instinctively prescribe solutions rather than describe problems, and agents now find better paths when given problems, not instructions.
"I'm just going to extend the pro case here a little bit just for the sake of the argument. I actually think for a while it was to my deficit to know as much as I know about programming because I was instructing the agents to do things as I prescribed them to do... Then I was a little late on the next moment. And the next moment allowed me, allowed anyone to describe outcomes, to describe problems to the agents and get better solutions than if you had a programmer prescribe the path." 00:58:02
Parallel Multi-Machine Agentic Setups Are the New Productivity Architecture
DHH describes moving from one agent to 16 parallel threads across multiple physical machines connected via Tailscale and managed with a tool called Herder. This is the infrastructure pattern he found necessary to reach genuine productivity multiplication.
"I looked in my closet and I realized I had a bunch of mini PCs from prior experiments. I just said, what if I just connected all of them? Oh, wow. And I just connected four of the computers in a closet. They all had their little comet. And suddenly I could run agents on more computers at the same time... at about four to five machines running, I don't know, three agents. I have about 16 threads." 01:43:41
The Innovator's Dilemma Is Playing Out in Real Time Against Incumbents
DHH applies classic innovator's dilemma framing to explain why Adobe, Microsoft, and other incumbents cannot accelerate despite owning the resources. Their management layers and processes are tuned for an era that no longer exists, and super-tankers cannot pivot.
"This is the classic innovators dilemma. These companies have gotten so good, so established at the old way, and therefore their entire structure, management layers, processes are tuned for a time that no longer exists. But you can't pivot that. These are super tankers. It just doesn't happen." 00:29:33
Open Source Is Now at Its Greatest Moment Ever — and Maintainers Are Complaining
DHH inverts the common lament about AI-generated pull requests flooding open source, calling it the actual fulfillment of open source's original promise: global collective intelligence contributing to shared software. He merged over a thousand pull requests in three months on Omachi, using agents to triage them.
"I've been running this Zomachi project now for a little over a year. And in the last three months working on Quattro, I have merged over a thousand pull requests. Quite a lot of those pull requests were written by people who were not classical programmers or were programmers in other domains... They were able to contribute their good ideas because of agents." 00:39:55
The Economic Argument for Beautiful Code Is Now Premised on Token Scarcity
DHH reveals that the reason to maintain clean, beautiful architecture is no longer aesthetic or human-readability — it is now a token economics argument. Well-structured code keeps agent context cheap. As tokens get cheaper, even this argument weakens.
"There is great payoff to writing systems that agents have an easier time dealing with and evolving without having to relearn the entire context. Just like humans. If they can make iterations and changes to the code base without wrecking the architecture, they can make the next change just as cheap as the last one." 01:07:52
AI Can Now Generate Novel Ideas, Not Just Regurgitate
DHH states flatly that he has been humbled by ideas emerging from current models that he would not have originated himself — reversing his prior belief that all creative direction must come from humans.
"I have seen things you people wouldn't believe. Ideas coming out of models so great that it makes me humble as a person who otherwise prides himself on having good ideas. The agents are incredibly capable of creative thought. And folks who are still stuck in the analysis that agents are parrots, just regurgitating the ideas that are already there are delusional about the progress that's been made in the last six to nine months." 00:42:24
2. Contrarian Perspectives
Vibe Coders May Actually Be Better at Agentic Engineering Than Experienced Programmers for Certain Problem Classes
Most people assume programming experience is a prerequisite for effective agentic engineering. DHH argues the opposite is true for product-oriented tasks: product managers, designers, and non-programmers who describe desired outcomes rather than prescribed implementations may get better results because they don't contaminate the prompt with their own technical assumptions.
"There are plenty of programmers who are not very good product managers. Software is product management. What should it do? Who should it do it for? How should it do it? How should it look? What's our priorities? What do we start with first? What does version one include? All of those skills are not easily or equally distributed across all programmers. And in the agentic era where you are letting an agent and AI do the implementation, these are the skills you need." 01:36:18
The Frontier Can Be Caught Up in Two Weeks — FOMO About Missing the AI Wave Is Irrational
The conventional anxiety is that if you weren't following every model release and framework shift over the past year, you're hopelessly behind. DHH's view is the opposite: there is no compounding knowledge stack to miss, and a developer returning from a year-long backpacking trip can be fully current within two weeks.
"If you missed the past year, you can catch up to the frontier in two weeks. If you're a programmer who was out hiking the Himalayas for a year and you come back, you can catch up in two weeks. And this is actually a great credit to the progress we're experiencing. We have so many experiments running simultaneously right now that are constantly and ruthlessly sorting what works, what doesn't work. You don't have to remember or even be part of that entire journey. You can just show up for the results." 01:29:51
AI Is Already Better Than Most Human Open Source Contributors
The default narrative is that AI-generated pull requests are noise that burden maintainers. DHH, drawing on reviewing tens of thousands of human submissions over 25 years, argues the median AI pull request already exceeds the median human pull request on every quality dimension — documentation, testing, correctness — and has the added benefit of zero emotional cost when rejected.
"I would rather get an agent-written pull request to one of my projects than I'd get one written by a human. And it's not just because the quality is better. It's also because I feel a lot less bad if I just reject it. You didn't even write it. So I could simply look at what your agent wrote on your behalf and go, eh, don't want it." 00:37:53
The Model Safety Threat Is Inverted: Fable Was Too Capable to Release
The public narrative on AI safety focuses on alignment and values. DHH points to a different and more immediate threat vector: Fable was reportedly withheld from release because its security vulnerability exploitation capability was so advanced it would have been a direct weapon for attackers — exceeding most state-sponsored human operators.
"This model was so capable of finding holes that a attacker could exploit that it was simply not safe to release. So the irony here is that when you look at that field, it seems like we've reached levels of intelligence that virtually no human can match because many of these security holes are about stringing combo moves together." 00:20:12
Planning Your Career Around AI Trajectories Is a Waste of Time — Even for the Smartest People in the Industry
While conventional wisdom says you should be strategically positioning for the AI future, DHH argues that trajectory prediction is so unreliable that career planning around it is actively harmful, producing anxiety without useful signal. The only rational strategy is full present-tense engagement.
"Don't try to anticipate anything. You will literally go crazy because even the smartest brains in the business cannot anticipate what two model hops from here is going to look like. It's an absolute waste of time and you will develop an AI psychosis trying to deduce what two years from now it's going to look like. Focus on right now." 01:23:11
3. Companies Identified
Anthropic
AI safety company and model lab, creator of the Claude family of models. Mentioned as the primary model powering DHH's agentic workflow; Claude Code (the CLI agent harness) was the tool that crossed the threshold into genuine productivity. Opus 5 and Fable represent the current frontier.
"I don't think I installed Cloud Code until September. So there was about six months there where pioneers saw these glimmers of what the future was going to look like." 00:50:24
37signals
Software company (Basecamp, Hey) founded and run by DHH. Mentioned as the production environment for agentic engineering experiments; Basecamp 5 was the first product released with agent acceleration.
"We just released Basecamp 5 not too long ago. That was the first product at 37signals that was really agent accelerated." 00:22:02
Shopify
E-commerce platform, CEO Toby Lütke. Mentioned because Lütke saw the agentic shift months before DHH and issued an internal AI memo; also credited with employees having breakthrough agentic experiences over the 2025 Christmas break.
"Toby, Toby Lutka, the CEO of Shopify and now my partner in crime on this Omachi project in part, he's gotten pilled with Omachi as well. He saw these things very early and he tried to tell me." 00:50:48
Omachi (Umachi)
Arch Linux-based desktop operating system created by DHH; described as a beautiful, opinionated Linux alternative to macOS and Windows. The Quattro release was built 100% by agents, with 1,000+ pull requests merged in three months. DHH describes it as the proof-of-work that agentic engineering is real.
"Umachi Quattro launched on Friday. It's been downloaded by tens of thousands of people and they like it. They like it a lot." 00:44:49
Tailscale
Networking company that creates WireGuard-based mesh VPNs. DHH describes Tailscale as a revolution for multi-machine agentic setups, allowing him to connect all machines across his Malibu and Copenhagen offices into a single local network without firewall configuration.
"Tail scale is essentially turning all the computers you have into a local network wherever you are. Like right now on my phone, I have direct access to all the computers in my Malibu office." 01:42:47
GL.iNet (Comets)
Hardware company making KVM-over-IP devices. DHH specifically names their "Comets" product as the key hardware enabling frictionless multi-machine agent setups — plug in HDMI and USB, join Tailnet, control remotely through a webpage.
"I bought these amazing KVMs called GLI.net Comets. And what they do is it's this little box. You plug in HDMI, you plug in USB and connect it to the computer... You connect this thing in, you go to a webpage, log in one, set one password. Now this thing can hop on your tail net." 01:42:19
Herder
Terminal-based agent management tool. DHH describes it as Tmux plus agent notifications — it alerts the human when an agent needs a decision and tracks which agents are active, enabling true parallel agentic workflows.
"I've switched to this thing called Herder. And Herder is essentially Tmux plus agent notifications. So whenever your agent is done and needs something for you, it goes ding! A little bell telling you it's ready for its human." 01:41:19
Blitzy
AI-powered autonomous software development platform for large enterprise codebases. Mentioned as a sponsor but described as a company attacking the same parallel-agent problem DHH is solving personally, but at enterprise scale with 80%+ autonomous code delivery.
"Built, designed, customized for large, complex code bases, works with large companies to ship software much faster via a lot of agents working together." 00:03:51
Analogue
Hardware company run by Palmer Luckey as a side project recreating vintage gaming consoles with modern screens and low input lag. DHH specifically highlights the Chromatic (Game Boy recreation) and their Nintendo 64 recreation as examples of passionate craftsmanship.
"Palmer Luckey's side geschäft, which is recreating old consoles... they just put out the Nintendo 64 too. Incredible. Super cool. Wild attention to detail, input lag, and all the other things." 01:11:20
TextMate
Code editor used by DHH for nearly 20 years (2005 onward) until switching to Linux. Cited as the anchor of hand-crafted programming before the agentic era.
"It's crazy to think about now, but yeah, I used TextMate for almost 20 years. I used TextMate starting in 2005, I think I helped get the first version out." 01:37:57
OpenAI
AI lab, creator of GPT series including GPT Sol (o3/Codex). Mentioned alongside Anthropic's models as part of the current frontier enabling the third phase of the agentic era.
"This summer, with Opus 5, Fable, and Sol, GPT Sol, and to a lesser extent, some of the open weight models, we've arrived at a new era." 00:17:11
4. People Identified
Toby Lütke
CEO of Shopify. Described as an early adopter who saw the agentic shift months before DHH did and issued a company-wide AI memo. Now described as DHH's "partner in crime" on the Omachi project, having become a Linux convert. Distinguished as a rare engineering-minded CEO with genuine technical instincts.
"I remember actually reading his memo to the company, the AI memo, and thinking, ah, it seems a little much. You're making a big deal out of something that I cannot yet feel is a tangible thing." 00:51:11
Ryan Hughes
DHH's primary collaborator on the Omachi project from near the beginning. Described as key to building the community and ambition around the project; the conversation with him about ambition inflation from "don't crash at 3am" to "take over the world" is cited as emblematic of the agentic era's possibilities.
"I was just talking to Ryan Hughes, who's been my main partner on Omachi almost since day one. And we were literally talking about yesterday how when we started on this journey together, our ambitions were very modest." 01:24:24
Palmer Luckey
Founder of Oculus, now running Analogue as a side project recreating vintage gaming hardware. Mentioned by DHH as someone producing extraordinary work in hardware recreation with obsessive attention to detail.
"One of my favorite video games of late is Mott Retros. Do you know Palmer Luckey's side geschäft, which is recreating old consoles? So he's recreated the Game Boy." 01:11:20
Jeff Bezos
Founder of Amazon. Referenced for his "regret minimization framework," which DHH adopts as his personal mental model for deciding how to respond to the AI transition.
"Again, I keep coming back to this almost regret minimization framework to borrow Jeff Bezos' terms here. Are you going to look at yourself two years from now and think, oh, I spent my time well being pissy about the present?" 01:36:43
5. Operating Insights
Vague Prompts Beat Detailed Specs — Iterate From a Working Prototype
DHH explicitly prescribes resisting the urge to specify upfront. The right operating posture is to give the minimum description necessary to get something running, interact with it, and discover your real requirements from usage. Over-specification front-loads decisions humans are not equipped to make before seeing the product.
"In the agentic age, you should resist the temptation to be overly specific upfront. Be as vague as you can to manifest something. Then interact with the something. The way you arrive at good software is you write a little bit of software and then you try to use it. It is in the process of using software that you discover what you really want." 01:03:53
Build for One User First, Then Put It on GitHub — The Agent Handles the Rest
DHH's playbook for going from personal tool to public open source project requires no additional human effort: simply instruct the agent to publish to GitHub. The agent writes the readme, sets up releases, and manages maintenance more diligently than most humans would.
"By the time you're done building the tool for yourself, you simply tell your agent to put it on GitHub. It will figure out how to put that repo on GitHub. It'll write a nice readme. It'll start using GitHub releases so that you can track things. It'll actually be a better software maintainer than you could ever be because it is far more patient." 00:34:35
Use Agents to Triage Agents — Apply AI Review Before Human Review
At scale, DHH no longer reviews pull requests himself. Agents pre-screen all incoming PRs, filtering duplicates and bad submissions, and only surface decision-ready items requiring a human merge/no-merge judgment. This is the operating model he uses to manage 400+ open PRs on Omachi.
"I'm not reviewing every pull request anymore. I haven't been reviewing them for quite some time now. I have the agents review them for me, and then they will give me a summary about whether something is ready for the decision, the human decision. Should we merge or should we not merge?" 00:40:47
Run Multiple Physical Machines, Not Just Multiple Tabs
DHH found that running multiple agent threads on one machine created resource contention that limited parallelism. The breakthrough was distributing across multiple physical mini-PCs connected via Tailscale and GL.iNet Comets, reaching approximately 16 simultaneous threads before hitting his own human processing limit.
"I don't know, three agents. I have about 16 threads. That's what I can run. And the faster the agents run, of course, the fewer threads I can run. But at the current pace, I can run about 16 threads at full acceleration." 01:44:08
The Architecture Must Stay Clean — But Now for Token Economics, Not Human Readability
DHH reframes why code quality still matters: it is no longer about human maintainability but about keeping agent context cheap. A clean architecture means agents can make incremental changes without reloading full context, keeping the marginal cost of each iteration constant. A ball-of-mud codebase makes every subsequent agent task more expensive.
"There is great payoff to writing systems that agents have an easier time dealing with and evolving without having to relearn the entire context... If they can make iterations and changes to the code base without wrecking the architecture, they can make the next change just as cheap as the last one." 01:07:52
6. Overlooked Insights
Fable's Suppression Is a Signal That AI Offensive Security Capability Has Already Crossed a Threshold
DHH mentions almost in passing that Fable — an Anthropic model — was not released publicly because its ability to find and chain security vulnerabilities was so advanced it was deemed a direct weapon. This is not framed as a hypothetical future risk. It is presented as a capability that already exists and has already been withheld. The implication is that the gap between frontier AI security capability and human defensive security is already large, and the most powerful tools in this domain are being deliberately kept off the market. For investors, this suggests that AI-powered defensive security companies have an urgent, widening moat — but also that the offensive risk landscape is already far ahead of what public discourse acknowledges.
"This model was so capable of finding holes that a attacker could exploit that it was simply not safe to release. So the irony here is that when you look at that field, it seems like we've reached levels of intelligence that virtually no human can match because many of these security holes are about stringing combo moves together... Humans who are able to do that are very rare. They usually work inside state-sponsored organizations or other clandestine operations." 00:20:12
Omachi's Plugin/Skills Architecture Is the Missing Layer That Enables Non-Programmers to Extend an OS
DHH briefly mentions that Omachi ships a "skills" system — a set of structured instructions that tells any agent how to create extensions, panels, and UI components for the operating system. This is architecturally significant and almost entirely unremarked upon: it is the equivalent of an app store API, but for agentic contributors. Any user with an idea and an agent can extend the OS without knowing the underlying stack. If this model works at scale, Omachi becomes the first operating system with a genuinely agentic contribution layer, which is a fundamentally different distribution and development moat than any existing platform.
"Amachi ships a set of skills that tells any agent you bring to it how to create extensions to the operating system and therefore affording you the vision of the true malleable... I've never seen that many people be able to create software that's meaningful for them. Also be usable for others so quickly." 00:54:25