DHH Says Writing Code by Hand Is Over. Is He Right — or Just Another AI Hype Man?

Last week, David Heinemeier Hansson — DHH, the creator of Ruby on Rails — walked onto the stage at Rails World in Austin, Texas, and told a room of more than a thousand Rails developers that writing source code by hand is over. It’s no longer economically viable. It’s time to stop being a loser.

By some accounts, people cried.

For anyone who came up through Rails, the moment lands strangely. Rails was my first framework. It launched my career in software development. Watching that keynote felt like watching your childhood home get demolished to build a data centre.

And there’s an obvious contradiction at the heart of it. DHH — the man whose entire brand was developer happiness, convention over configuration, the joy of rails new — used his keynote to promote AI-generated Rust. That’s roughly like the Pope showing up on Easter to explain the benefits of atheism.

So is he right? Or is he just another hype man with AI psychosis?

The way to answer that is to go through the skills programmers actually have and ask, one by one, whether they still matter.

Keyboard Martial Arts

Start with the most vulnerable skill: keyboard martial arts.

A couple of years ago, it was very much in vogue to get good at tools like Neovim. Memorising hundreds of shortcuts, spending hours perfecting a config that let you write code measurably faster. There was genuine prestige in it.

If an agent is making most of your code edits now, being able to delete the contents of parentheses in three keystrokes without touching your mouse is becoming a niche party trick.

That said, DHH is himself a Neovim user and still a big proponent of command-line interfaces — with one enormous caveat. In the keynote he argued that every application developer should ship a CLI. Not for humans. For agents.

“It is your obligation to deliver those CLIs by next Friday, so I can use your application without actually ever having to touch it.”

The bottom line: editors and CLI tools still have a place. But investing enormous time mastering them is no longer a path to being a more productive developer.

Frameworks

What about frameworks? Rails, React, Svelte, Angular, Tailwind — the whole zoo. All of them built cult followings. At least they used to.

Rails explicitly put programmer happiness at the centre of its philosophy. And there’s a real memory there: running rails new in 2008 felt like holding a magic wand. A full MVC CRUD application in seconds.

The harsh reality is that developer happiness is dead — or at least, it’s no longer the organising principle. Any framework or language built around that idea is going to have a hard time.

DHH himself was a certified Rust hater. His verdict, years ago: “This is an awful, awful, awful programming language when you subject humans to write it. Absolutely inhumane.”

Then in the keynote, he announced that Hey — their email app — is being rewritten not with human-powered Ruby on Rails, but with pure AI-generated Rust.

“Rust is amazing if you never, ever, ever have to look at it yourself.”

The rewrite cut CPU and memory usage on the server by 95%. And that’s the point worth taking seriously. The frameworks that survive will be the ones that require the fewest tokens — and therefore cost the least — or the ones that achieve the highest performance. Developer happiness is almost a non-factor now.

Which points toward something stranger: over the next decade, maybe sooner, frameworks, languages, and runtimes may converge toward a single universal toolchain. A language optimised for tokens. One that no human needs to understand.

Coding

Now the big one. Actually writing the source code.

DHH claims he went from writing roughly 30,000 lines of Ruby a year to around 150,000 lines a month using agents. He’s one rich, slightly crazy guy — so he also polled the room. Out of 1,200 developers, how many spend a material amount of time each week writing code by hand?

About five hands went up.

If you trust a show-of-hands poll, that means less than 1% of humans in that room are still writing code manually. The end of coding isn’t near. It’s here.

Except something doesn’t add up. If coding really is dead, why haven’t there been mass layoffs? Why are Silicon Valley companies still hiring developers with six-figure packages?

What Was Actually Valuable All Along

Here’s the thing the doomsayers keep missing. Writing code — or any skill tied to mechanical execution — was never that valuable to begin with.

What has always mattered, and still matters, is the ability to define a problem and then design a system that solves it securely and efficiently. Agents just make that process dramatically faster.

So when DHH told the room to stop being losers, he probably wasn’t calling people losers for writing code by hand. He wasn’t calling them losers for still loving Rails. He was calling them losers for their pessimism.

Because you have an army of coding robots at your disposal and you’re blackpilling? There has never been a better time to be an idiot with an idea.

That’s the real message buried under the provocation. The black pill is for losers. Not because pessimism is unfashionable, but because it’s now demonstrably wrong. The barrier between having an idea and shipping it has never been lower — and the people who can see that are going to build things the rest of us haven’t imagined yet.

The Honest Verdict

So — is DHH right?

Partly. Mechanical execution is being commoditised fast, and anyone whose entire value proposition was typing speed is in trouble. Frameworks that exist primarily to make typing pleasant are losing their rationale. Command-line tools are being redesigned for machines rather than humans.

But the conclusion he’s pushing — that coding is over, that developers are obsolete — is a headline, not an analysis. The skill that’s dying is the keystrokes. The skill that’s thriving is judgement: knowing what to build, how to make it safe, and how to tell when the machine has quietly made something terrible.

Charlie Chaplin put it better than any keynote: you’ll never find a rainbow if you’re looking down.

Don’t look down.