DHH Just Said the Quiet Part About AI Out Loud. Developers Are Furious.
In this article
Bottom line: On September 23, 2026, DHH opened Rails World in Austin by saying 37signals had gone "pencils down" on hand-written code.
He called hand-writing code "no longer an economically productive enterprise for the vast majority of programmers working at the vast majority of companies." The company now has AI agents, including Claude Opus and Gemini Flash, produce most of its implementation.
The backlash is mostly about jobs, not code quality, and the practical question is which parts of your work stay yours once an agent writes the diff.
I spent three years telling anyone who'd listen that AI-written code was a demo trick. I said it in code reviews and in a Slack thread I'd now like to delete.
Last week a man who has been shipping Rails since before most of my team could drive stood on a stage in Austin and said the argument is over.
I'm not here to tell you he's right. I'm here to tell you what he actually said, why it landed like a brick through a window, and what I'd do on Monday if I were you.
What DHH Actually Said
The facts first, because the internet has already compressed them into mush.
In the opening keynote of Rails World 2026, David Heinemeier Hansson declared that 37signals had gone "pencils down" on writing code by hand.
The line everyone is quoting is the economic one: hand-writing code is "no longer an economically productive enterprise for the vast majority of programmers working at the vast majority of companies."
Note the framing. He didn't say hand-written code is worse or that it's impossible. He said it doesn't pay, which is a much harder claim to argue with and a much more uncomfortable one to hear.
At 37signals, agents like Claude Opus and Gemini Flash now produce most of the implementation. Humans still decide what gets built and review what comes back.
Then he went after the standard defense. When developers say "AI slop," he argued, they're often clinging to a comfort blanket.
His read is that programmers who pretend nothing has shifted are the ones in trouble.
He framed "slop" as a stage between anger and bargaining on the way to acceptance. The reactions on X ran from stages-of-grief memes to careful rebuttals.
Why This Is the "Quiet Part"
Plenty of people have said AI writes code now. What makes this different is who said it and what he skipped.
DHH is not a startup founder with a seed round to justify. He built Rails, he runs a profitable, famously anti-hype company, and he has spent two decades mocking trends.
When that person says "pencils down," the usual dismissal ("he's selling something") doesn't work.
The quiet part is the economic claim underneath.
Most AI discourse dances around it with phrases like "augmentation" and "copilot." DHH said the unit economics of a human typing implementation are over for most teams, and that's a statement about payroll.
The Backlash Is About Rent, Not Style
Here's the sharpest response I've read. antirez, the creator of Redis, argued that much of the "AI slop" panic is really labor-market panic.
Developers tolerated slow frameworks and needless complexity for years when it didn't threaten the paycheck.
So if you're afraid about invoices and family, say that, instead of laundering it as aesthetics.
I think that's right, and it stung because I recognized myself. Half my "AI code is unmaintainable" arguments were true. The other half were fear in a lab coat.
Both things can hold at once:
- DHH can be right about the economics and still be selling a tidy story about a company with a tiny, senior, hand-picked team.
- Developers can be right to be furious even if the code coming out of agents is decent. Quality was never the real fight.
Reality Check: What a Keynote Doesn't Tell You
I want to be careful here, because a stage talk is a highlight reel. A few things I don't know and you shouldn't assume:
37signals is not your company. They're a small, senior team with a decades-old, conventions-heavy codebase.
Rails is close to the best-case framework for agents, because convention means the model has seen your architecture ten thousand times.
"Most of the implementation" isn't "most of the work." Deciding what to build, reviewing diffs, owning incidents and saying no to features all stay human.
If your job is 20% typing, a 90% cut in typing is a big deal but not an extinction event.
Review is the new bottleneck. An agent can produce a 600-line diff in four minutes. Somebody still has to understand it, and that person needs the exact skills hand-writing code used to teach.
That last point worries me most, and I've written before about the productivity traps in vibe coding. If juniors never write the code, where do the future reviewers come from?
Nobody on that stage had a clean answer.
What I'd Actually Do Monday Morning
Skip the argument about whether DHH is right. Run the experiment on your own codebase instead. Here's the workflow I'm using, and it's boring on purpose.
1. Measure your own typing share
For one week, track how much of your time goes to writing implementation versus reading, debugging, deciding and talking.
If it's under a third, the "pencils down" headline affects you less than the memes suggest. If it's over half, pay attention.
2. Hand an agent a bounded task, not a vision
Pick a ticket with clear acceptance tests. Give Claude Opus or your agent of choice the spec, the tests and the relevant files.
Then read the diff like you'd read a stranger's pull request, because that's what it is.
3. Write the tests yourself
This is where I'd keep my pencil. Tests are the spec. If the agent writes both the code and the tests that bless it, you've built a machine that agrees with itself.
4. Protect the apprenticeship
If you lead a team, make sure juniors still write real code on real problems, and make reviewing agent output a taught skill instead of a chore.
The industry is about to find out what happens when you stop training the people who'll catch the bugs.
5. Name your fear out loud
antirez's point applies to all of us. If your objection is "I'm worried about my job," say it plainly, because then you can plan around it.
An objection dressed up as "code quality" gives you nothing to plan around.
Where I Landed
I don't think DHH said something false. I think he said something true that most of us weren't ready to hear from someone with that much credibility.
The economics of typing code are shifting, and pretending otherwise is a strategy with an expiration date.
But I also don't think "pencils down" means "brains off." The valuable work moves up the stack to specs, tests, review, architecture and judgment about what's worth building.
Those are skills you can start building today, with or without agreeing with a keynote.
I was wrong for three years, and I'd rather be wrong early and adjust than be right about something that stopped mattering.
So here's what I want to know: if an agent wrote 90% of your last pull request, which 10% would you refuse to hand over, and why?
Sources:
- DHH says 37signals has gone pencils down on writing code by hand (Startup Fortune)
- DHH Declares End of Hand-Writing Code at Rails World 2026 (daily.dev)
- DHH Declares End of Hand-Writing Code at Rails World 2026 (X trending)
