The State of Rails: A Post-Programming Era?

By Jared Norman | Published September 24th, 2026

Despite the shifting tides of the industry, David Heinemeier Hansson (DHH) remains the guiding force behind Ruby on Rails. For those of us who build for clients using this stack, his trajectory isn't just interesting—it's consequential.

At the Rails World 2026 opening keynote, DHH unveiled a future that feels less like an evolution and more like a departure.

The "Retirement" of the Programmer

DHH made a startling claim: he is a professional programmer he has retired from professional programming.

To be clear, he hasn't stopped building software; rather, he has redefined the act of creation. He now posits that English is the premier programming language, facilitated by Large Language Models (LLMs). In this new paradigm, the human doesn't even need to audit the resulting code.

"Writing code by hand is no longer an economically productive enterprise for the vast majority of programmers working at the vast majority of companies."

The Great Pivot: From Web to Native

This shift has fundamentally altered his technical preferences. DHH has historically championed the "small team, ambitious product" ethos of the Rails web stack. However, he now views native applications differently.

Because LLMs handle the heavy lifting, DHH is now embracing Rust. While he still finds the language's syntax "hideous," he no longer cares because he isn't the one reading it. He values the stability and speed it provides, provided the LLM is the one navigating the complexity.

By the Numbers: The LLM Explosion

DHH provided some staggering (if debatable) statistics regarding his output:

• Pre-LLM Era: $\approx 30,000$ lines of code per year.
• August 2026: $\approx 150,000$ lines of code in a single month.
• Language Distribution: Ruby, which once comprised 50% of his work, now accounts for only 3%.

// Example of the "hideous" but performant code DHH now accepts
fn main() {
    println!("The LLM wrote this, so I don't have to read it.");
}

A Vision of Agents and "Black Pills"

DHH envisions a world where humans reading code is the exception—similar to how we only look at stack traces in Sentry when something breaks. He predicts this will be the standard for nearly all companies by the end of the year.

Furthermore, he advocates for a universal shift toward CLIs (Command Line Interfaces). The goal isn't for humans to type more, but for AI agents to interact with services without the friction of a GUI.

He concluded his talk by addressing the psychological state of the industry, urging developers to abandon AI skepticism:

"The black pill is for fucking losers."

The "Rails-Shaped Hole"

There is a glaring irony here: DHH used the premier Rails conference to announce that Hey, one of his flagship products, is leaving the Rails stack.

The Paradox of 37signals

The strategy for the new version of Hey is to build six separate native apps because "web fidelity" isn't sufficient. This creates a confusing contradiction:

If the primary interface for every product becomes an agent driving a CLI, the "opinionated UI/UX" that differentiates 37signals products (like Basecamp or Fizzy) vanishes. What stops a user from switching to the cheapest possible alternative?

Is Rails Finished?

The vision for Rails has narrowed significantly. It is now framed as a "great fit for web apps" and a "good target for AI." But this feels like a placeholder rather than a roadmap.

• Define a vision beyond "token efficiency."
• Address the gap left by the creator's lack of attention.
• Compete with frameworks like Hanami (which has a clear Ruby web roadmap).
• Navigate the political and technical schism caused by the Mosscap fork.

While Shopify and others maintain the day-to-day health of the framework, DHH has always been the visionary. Now, he seems to be arguing himself out of his own business.

Final Thoughts on the "Product" Approach

37signals succeeds because of marketing and product intuition, not by solving "hard" computer science problems. Building a Kanban board isn't a technical marvel; it's a product decision.

DHH's approach—ignoring the output and evaluating only the result—works for simple apps. However, his presentation of these shifts as "settled" is logically shaky. He compares 150k lines of verbose Rust to 30k lines of concise Ruby, then admits the comparison is unfair, yet maintains the conclusion.

In the end, the creator of Rails spent his keynote telling Rails developers that the act of developing—the very thing that built the community—is becoming a relic of the past.