Rails Creator DHH Quits Hand-Coding: 'English Is a Better Programming Language'

DHH Says He Hasn't Typed a Line of Code Since March

David Heinemeier Hansson, co-founder of Basecamp and the creator of Ruby on Rails, has quit writing code by hand. The announcement came during an emotional keynote at Rails World 2026, where the programmer widely known as DHH told the audience that he has not typed a single line himself since around March 2026, ending a 25-year run as a professional programmer.

For an industry that has spent several years arguing about whether AI can genuinely produce production software, the timing matters as much as the content. DHH is not a peripheral observer drifting toward a new tool. He is one of the most recognizable working programmers of his generation, and he is now publicly stating that the manual portion of the job is finished for him.

A Startling Reversal, Not a Gradual Drift

What makes the shift notable is how recent the opposing position was. A little over a year before the keynote, DHH was openly pushing back against AI coding, questioning the case for handing the writing of software over to machines. His move is therefore not a slow adoption curve or a quiet experiment. It is a reversal, announced in public and framed in personal terms, by someone who had been among the more prominent skeptics.

That contrast is part of why the keynote carried weight with the room. Rails World is a gathering built around a framework he created, and the people in the audience are largely the developers who work with it every day. Hearing its author say he no longer writes the code himself is a different kind of signal than a vendor demo or a benchmark result.

The Economics of Typing Code Yourself

The core of DHH's argument is economic rather than purely technological. Manual coding, in his assessment, no longer makes sense for most programmers and most companies. He goes further than the current state of the tools: by the end of the year, he expects that logic to apply to practically every domain of software work.

That framing deliberately sidesteps the usual debate about whether AI-generated code is elegant, idiomatic, or secure in every case. The question he puts forward is simpler and more uncomfortable — if the work can be directed rather than typed, what does it cost an individual or an organization to keep typing it? For teams already under pressure to ship faster with flat headcount, that is not an abstract thought experiment.

'English Is a Better Programming Language Than Ruby'

The line that will likely outlive the keynote is his claim that English is now a better programming language than Ruby — the language his own framework is built on. It is a deliberately provocative way of describing a change in the layer where developers spend their time.

Instead of expressing intent through syntax and abstractions they must maintain, programmers increasingly express it through description, refinement, and review. Ruby remains the substrate for a large body of existing Rails applications, but in DHH's account the human contribution is migrating upward, from the mechanics of writing statements to the articulation of what should exist.

From Programmers to 'Professional Makers of Things'

Rather than treat the change as a loss, DHH framed it as the beginning of a new career phase. Programmers, in his description, become "professional makers of things," directing what he called intelligence that was only available in science fiction up until a few moments ago.

That reframing is aimed squarely at the anxiety running through the profession. The pessimist's version of the AI coding story is a slow erosion of a craft into prompt supervision. The version DHH presented is closer to an expansion of scope: more ambitious products, more surface area to build on, and less time spent on the mechanical translation of ideas into syntax.

Software Architecture Needs Rethinking

He also argued that software architecture itself has to be reconsidered. His reasoning is that traditional abstractions lose value when AI agents are the ones changing the code. Abstractions are a human compression technique — shorthand that lets people hold a large system in their heads. When the primary editor of a codebase is not a person, some of those shortcuts stop paying rent, while other kinds of structure become far more important.

He did not claim to have the answers. "No one yet has the blueprint," DHH said, adding that the audience gets to be present as the field defines these things. It is an unusually candid admission from a figure known for strong opinions, and it leaves the practical questions open rather than settled.

'The Biggest Thing in the History of Computing'

DHH did not hedge on scale. He called the shift the biggest thing that has happened in the history of computing. Coming from the author of a framework that reshaped how a generation of web applications were built, the label is meant to be taken literally.

Whether or not that framing holds up, the direction of travel is clear from his own behavior. A programmer with 25 years of accumulated skill and strong attachments to a specific language stopped typing — and described the change as something to build on rather than something to resist.

What This Means for Working Developers

For developers reading the keynote secondhand, the practical takeaways are less dramatic than the headline but still concrete:

• The value of raw fluency in a single language's syntax is declining relative to the ability to specify, review, and correct machine output.
• Architectural choices matter more, not less, because the people maintaining the reasoning behind a system may not be the ones editing its files.
• Assumptions about what "writing software" looks like day to day are being renegotiated in public, including by the people who defined the previous era's defaults.
• The economic argument is arriving faster than many expected, with DHH predicting near-universal applicability by the end of the year.

The Questions Left Unanswered

Nothing in the announcement resolves the harder problems: how code quality is verified at scale, what happens to junior developers who traditionally learned by writing thousands of lines by hand, and how teams keep systems comprehensible when agents are the ones making changes. DHH's own position is that there is no blueprint yet, which places the industry in an unusual moment — a major transition acknowledged by a leading practitioner, with the rules still being drafted.

What is no longer in question is his personal answer. After a quarter century of professional programming, the creator of Ruby on Rails says he is done writing code by hand, and he is inviting developers to treat that as an opening rather than an ending.

This article is based on reporting by The Decoder. Read the original article.