TubeReads

DHH's new way of writing code

Six months ago, David Heinemeier Hansson was openly skeptical of AI coding tools on Lex Fridman's podcast. Then, over winter break, something changed dramatically—he went «agent first» on everything. What triggered this complete reversal from one of the most opinionated and experienced builders in tech? And if a developer who values craft, aesthetics, and beautiful code above all else is now letting AI write most of his software, what does that signal about the shift hitting the entire industry?

Durée de la vidéo : 1:47:21·Publié 8 avr. 2026·Langue de la vidéo : English
11–12 min de lecture·21,418 mots prononcésrésumé en 2,327 mots (9x)·

1

Points clés

1

DHH's stance on AI didn't change philosophically—the tools simply became good enough. Opus 4.5 in late November 2024 was the inflection point where agents could consistently produce merge-worthy code at DHH's exacting quality bar.

2

Senior developers are seeing 5–10x productivity gains because they can validate agent output and redirect when needed. Junior developers, unable to assess quality at that level, are becoming more vulnerable as pure implementation work gets automated.

3

The real unlock isn't efficiency on existing work—it's tackling projects that would never have been started before. DHH's team is now optimizing the fastest 1% of requests (P1) and building features in days that previously would have taken months.

4

Ruby on Rails is experiencing a renaissance because it's one of the most token-efficient ways to build web apps, making it ideally suited for agent workflows. DHH believes aesthetics is truth: when code is beautiful, it's likely to be correct.

5

The constraint is shifting from implementation to product judgment. Developers who can't also do product thinking, talk to customers, and exercise taste will struggle, while those who combine technical depth with business sense become vastly more valuable.

En bref

We may have reached peak software engineer: AI agents are now good enough that senior developers can 5–10x their output, shifting the constraint from implementation to taste, judgment, and deciding what to build—making those who care deeply about craft more valuable, not less.


2

The Inflection Point: From Skeptic to Agent-First

Opus 4.5 in November 2024 changed everything for DHH overnight.

DHH's transformation wasn't philosophical—it was empirical. On Lex Fridman's podcast six months earlier, he had dismissed AI autocomplete tools as infuriating, like someone constantly interrupting mid-sentence. The models weren't good enough, and the ergonomics were terrible. Then Anthropic released Claude Opus 4.5 on November 27, 2024, and everything shifted.

The combination of a frontier model that could consistently produce merge-worthy code and agent harnesses that gave AI access to terminal tools created a new paradigm. DHH describes it less like managing a team and more like stepping into a «super mech suit» where he suddenly has twelve arms and can look at seven screens simultaneously. He's still the one doing the work—just hyper-accelerated.

Within weeks, DHH went from code-first (opening his editor, writing code, occasionally consulting AI) to agent-first (starting every project by instructing agents, reviewing their output, and making alterations only when needed). The speed of this shift shocked even him. What took months or years to contemplate—like optimizing the fastest 1% of requests—now happens in days as side projects.


3

The Unix Philosophy Validated

CLIs and agent harnesses prove the 1971 Unix philosophy was right all along.

💡

The Unix Philosophy Validated

DHH realized that building CLIs for products like Basecamp, Hey, and Fizzy wasn't just about making them easier for agents to use—it was about validating the fundamental Unix philosophy from 1971. Small tools that interoperate with pipes can now be orchestrated by agents across GitHub, Sentry, Basecamp, and more. An agent can check errors in Sentry, post a write-up to Basecamp, create a GitHub pull request, and comment back—all autonomously. The 50-year-old design pattern is suddenly the cutting edge of AI orchestration.


4

How DHH Works Today

Two models at different speeds, constant review, and git diffs.

1

Start with agents DHH opens a split-screen layout: NeoVim editor on the left, OpenClaw running Kimmy K25 on top right, Opus in ClaudeClaw on bottom right, and a terminal strip at the bottom. He tells one or both agents what he wants.

2

Review the diff He switches to NeoVim and uses LazyGit to review the changes. If the code looks correct and matches his aesthetic standards, he commits immediately. If not, he either instructs the agent to revise or edits the code himself.

3

Iterate or merge The ratio of agent-generated code he merges as-is has skyrocketed. Early on, he spent hours writing code himself. Now, agents produce the first draft, and he supervises. The speed is intoxicating, but he's careful not to treat it like a limited sale—it's sustainable, not a sprint.

4

Run multiple agents in parallel For complex problems, DHH sometimes has two frontier models—Opus and another—ping-pong on a plan, critiquing each other's approach. Once the plan is solid, he kicks off execution. This is how he tackled adding dual-boot support to his Linux distribution, Omachi.


5

The 100 Pull Requests in 90 Minutes

Claude reviewed a backlog that would have taken a week in under two hours.

I went into GitHub and we had I don't know 250 PRs pending and I kind of just sighed a little bit… I just asked Claude to review URL and the URL is the issue or is the PR. In 90 minutes, I think it was, I processed 100 PRs. And it wasn't that I merged all of them. In fact, I'd say I merged a small minority. Maybe 10% got merged as is. Then maybe 20% got merged but with Claude's implementation… This would have been a week's worth of work, days at the very least. What the heck? And even more than that, Claude's analysis of at least half the issues pertained to things I knew nothing about where it was undeniably a smarter, better reviewer, programmer that I could ever dream to be.

David Heinemeier Hansson


6

The Projects That Would Never Have Started

🚀
P1 Optimization
Jeremy, a senior developer at 37signals, optimized the fastest 1% of requests—taking 4ms responses down to under 0.5ms. This project would never have been prioritized before because the ROI seemed too low. With agents, it took a few days as a side project.
💾
Omachi Dual Boot
DHH wanted to add dual-boot support to his Linux distribution but considered it too finicky and high-risk to tackle manually. He had agents ping-pong a plan, then execute it. The criticality was high, but the time investment became feasible with AI assistance.
🛠️
Basecamp CLI
Building a full CLI for Basecamp so agents can interact with it natively was never a priority. Now, with agents able to scaffold and implement faster, 37signals is building CLIs for Basecamp, Hey, and Fizzy to unlock full agent accessibility.

7

Senior vs. Junior: The Widening Gap

Senior developers are 5–10xing productivity while juniors face an uncertain future.

SENIOR DEVELOPERS
More Valuable Than Ever
Senior developers are seeing the most dramatic productivity gains because they can validate agent output, redirect when needed, and assess whether code will work in production. Their taste, judgment, and architectural oversight are the new constraint. DHH notes that his most «agent-accelerated» people are the most senior—those who've internalized the craft deeply enough to know when AI is right or wrong.
JUNIOR DEVELOPERS
The Bottleneck Shifts Away
Junior developers historically learned by implementing features under senior supervision. But if agents can implement faster and more reliably, and juniors can't yet validate output quality, their role becomes tenuous. DHH points to Amazon's recent outages, which internal analysis traced to junior programmers shipping agent-generated code without proper review. Pure implementation work is being automated—those who can't also do product thinking, judgment, and quality assessment are increasingly vulnerable.

8

Aesthetics Is Truth: Why Craft Still Matters

Beautiful code is likely correct code—taste is becoming more valuable, not less.

DHH has always believed that aesthetics and correctness are inseparable. «When something is beautiful, it's likely to be correct,» he says, citing mathematics, physics, and software as domains where this principle holds. This philosophy is why he fell in love with Ruby—it produces the most beautiful code in his view, with an elegant balance of expressiveness and pragmatism.

In the age of AI agents, this philosophy becomes even more critical. Agents can generate working code, but can they generate beautiful, maintainable, coherent code that fits the grain of the system? Not yet—at least not without supervision. DHH won't merge sloppy agent output any more than he'd merge sloppy code from a junior developer. His bar remains sky-high, and that bar is what makes agent acceleration work for him.

This is why DHH believes standout designers and engineers who care deeply about craft will become more in demand, not less. As implementation gets commoditized, taste, judgment, and the ability to shape systems with intention become the differentiators. The constraint is no longer «can we build it?» but «should we build it, and what's the right way?» That's a deeply human question, and one that requires aesthetic sensibility as much as technical skill.


9

Designers as Product Managers and Implementers

At 37signals, designers figure out what to build and how to implement it.

Most companies treat designers as people who make specs look pretty. At 37signals, designers are product managers, implementers, and decision-makers rolled into one. They figure out what should be built, how it should work, and increasingly—with agent acceleration—how to implement it in CSS, HTML, and even JavaScript or Ruby.

DHH argues that when you combine these three roles—product thinking, visual design, and implementation—you get someone who understands the materials they're working with. They know how CSS stretches, how HTML structures, how the web wants to behave. It's like a jewelry designer knowing the properties of gold or an architect understanding load-bearing structures. Working natively in the medium produces better, more coherent results.

With agents, this model is becoming even more powerful. Designers at 37signals can now use AI to produce full working prototypes, not just as they'll be merged, but as a demonstration of the final shape and interaction. DHH recently hired a designer, Zoltan, who embodies this philosophy—someone who can think, design, and build fluidly across the entire stack. DHH believes this convergence of skills, now accelerated by AI, is the future of how great software gets made.


10

Peak Software Engineer: The Argument

We may have seen peak demand for programmers as pure implementers.

⚠️

Peak Software Engineer: The Argument

DHH's provocative thesis: we've likely reached «peak software engineer» in terms of the guild-like scarcity that commanded high salaries simply for knowing how to code. Before, programmers were the constraint—you couldn't ship without them. Now, agents are loosening that constraint rapidly. More software than ever will be produced (Jevons' paradox), but that doesn't mean all programmers are safe. Anywhere software is a cost center—which is most places—there will be intense pressure to cut headcount. The developers who survive and thrive will be those who combine technical depth with taste, business sense, and the ability to validate and shape what agents produce. Pure implementation is being automated. Judgment is not.


11

Ruby on Rails and Token Efficiency

💎
Token Efficiency
Ruby on Rails is one of the most concise, expressive frameworks for building web apps. That makes it highly token-efficient—agents can generate more functionality with fewer tokens, and the code is readable enough for humans to review and verify.
📖
Human Readability
Even as agents get better, DHH believes it still matters whether the code they produce is something humans can read, understand, and maintain. Ruby's readability and Rails' conventions make it ideal for agent-human collaboration, at least for now.
🔄
A 20-Year Legacy
Rails has been around for over 20 years, with a massive corpus of documentation, examples, and patterns. That makes it well-represented in training data, giving agents a huge knowledge base to draw from when generating Rails code.

12

The Intoxication and the Trap

Working with agents is so effective it's dangerously addictive.

When you can be this effective and impactful on an hour of supervision of these agents, it's really intoxicating. And I need to go, do you know what? This is not like a limited sale. AI is going to be here next month and the months after that. I cannot just operate as though it is a limited sale and I need to get all the dopamine harvested within the next two weeks.

David Heinemeier Hansson


13

Key Numbers from the Conversation

Data points that illustrate the scale and impact of DHH's AI shift.

Lines of Code in OpenClaw
400,000
DHH noted this used to take 10 years and thousands of developers. Now, agents can scaffold systems of this scale in weeks or months.
Omachi Contributors in 6 Months
400
DHH's Linux distribution, launched as a summer project, attracted 400 code contributors and tens of thousands of users in just over six months.
Pull Requests Reviewed in 90 Minutes
100
With Claude's help, DHH processed 100 GitHub pull requests in 90 minutes—work that would have taken a week manually.
37signals Team Size
60 people
Roughly 20 programmers, 10 designers, 14 customer support, and the rest in operations, HR, and finance. A small, focused team building multiple products.
Gmail Market Share in the U.S.
~80–85%
DHH estimates Gmail commands an unprecedented share of email traffic, making Hey.com's launch into that market all the more audacious.
Hiring Success Rate
~50%
Even with a rigorous, multi-stage hiring process, DHH estimates only about half of hires at 37signals work out long-term.

14

What Drives DHH: Love of Computers

Wealth and success never changed the mission—building with computers is the goal itself.

DHH has been financially independent for years, yet he works as hard as ever. Why? Because he genuinely loves computers. He's been obsessed since age five, whether playing video games, building software, or tinkering with Linux distributions. For him, wealth was never a checkpoint or a finish line—it was a byproduct of doing work he found deeply satisfying.

He rejects the notion that leisure is the ultimate goal. Psychological research consistently shows that purpose and mission are what make people happy, not passive consumption of free time. DHH has seen this pattern play out with every entrepreneur who sells their company, sits on a beach for three weeks, and then immediately jumps back into building something new.

Right now, DHH is more excited about computers than he's been in decades. Agent acceleration feels like the early 2000s when he first discovered Ruby—a time of pure creative possibility. He wakes up every morning intensely curious about what's happening in AI, what's possible today that wasn't yesterday. And while he's careful not to sacrifice sleep, health, or family time, he's leaning in hard. The mission remains the same: make things with computers, make them beautiful, and share them with the world.


15

Personnes

David Heinemeier Hansson (DHH)
CTO & Co-founder, 37signals; Creator of Ruby on Rails
guest
Gergely Orosz
Host, Pragmatic Engineer Podcast
host
Jason Fried
Co-founder, 37signals
mentioned
Toby Lütke
CEO, Shopify
mentioned
Kent Beck
Software Engineer & Author
mentioned
Steve Jobs
Co-founder, Apple
mentioned
Elon Musk
CEO, Tesla
mentioned
Lex Fridman
Podcast Host
mentioned

Glossaire
Agent HarnessA system that gives AI models access to tools like terminal commands, file systems, and APIs, allowing them to autonomously execute multi-step tasks rather than just generate text.
Token EfficiencyA measure of how much functionality or meaning can be expressed with fewer input tokens to a language model, which affects cost, speed, and context window usage.
P1, P50, P95, P99Performance percentiles: P50 is the median (50th percentile), P95 is the 95th percentile (only 5% of requests are slower), P99 is the 99th percentile, and P1 is the fastest 1% of requests.
Shape Up37signals' product development methodology, originally built around fixed six-week cycles with flexible scope, now being reconsidered as agent acceleration changes delivery timelines.
MCP (Model Context Protocol)A protocol for giving AI models structured access to external data sources and tools, which was a major focus in 2024 but is now being leapfrogged by CLI and agent harness approaches.

Avertissement : Ceci est un résumé généré par IA d'une vidéo YouTube à des fins éducatives et de référence. Il ne constitue pas un conseil en investissement, financier ou juridique. Vérifiez toujours les informations auprès des sources originales avant de prendre des décisions. TubeReads n'est pas affilié au créateur de contenu.