Summary: “The End of Coding” (Code Report)
Context and the creator’s premise
The creator recounts David Heinemeier Hansson (DHH) giving a provocative keynote at Rails World in Austin, Texas, claiming that writing Rails—or any source code—by hand is “over” and no longer economically viable. The creator frames this as both shocking (given DHH’s Rails legacy) and worth examining seriously, then sets out to evaluate which programmer skills will still matter as AI agents take over more “mechanical” coding work.
Skill 1: “Keyboard martial arts” (editors, shortcuts, CLIs)
The creator argues that deep mastery of tooling like Neovim, extensive keybindings, and speed-focused editor workflows is becoming less valuable because agents now make many code edits. These skills still have a place, but are increasingly “niche” rather than a major productivity advantage.
They also highlight DHH’s push for command-line interfaces (CLIs)—with a twist: DHH wants CLIs not primarily for humans, but so automation/agents can operate apps without a person touching the UI.
Skill 2: Frameworks and “developer happiness”
The creator contrasts the earlier era where frameworks like Ruby on Rails felt like “magic” (rapid scaffolding, strong conventions, “programmer happiness”) with a future where that value proposition matters less.
They claim frameworks may increasingly be judged by:
- Token efficiency (cheaper to generate/modify with AI)
- Performance (runtime efficiency that reduces infrastructure cost)
In this view, “developer happiness” becomes a minor factor compared to cost and performance constraints driven by AI-based development and deployment economics.
Skill 3: Language choice and AI-generated Rust
A central example is DHH’s reported pivot to AI-generated Rust. The creator notes DHH previously criticized Rust as “inhumane” for humans to write, but now praises it if humans don’t have to read it.
The creator repeats DHH’s claim that rewriting parts of the Hey email app in Rust led to about 95% reductions in CPU and memory usage, using it as evidence that future tech stacks may optimize for performance and AI-generation efficiency, not human ergonomics.
They also speculate that over time, ecosystems may “converge” toward something like a universal language optimized for AI/token constraints—potentially not designed for human readability at all.
Skill 4: Writing code by hand vs. higher-level engineering
The creator describes DHH’s claim of moving from writing roughly 30,000 lines of Ruby per year to producing around 150,000 lines per month with agents.
They also share an informal audience poll implying that very few developers still spend a “material” amount of time writing code manually—used rhetorically to argue that “the end of coding” may already be here.
However, the creator explains why developer demand and high pay can still persist: manual code typing was never the most valuable part. Instead, they argue the durable, high-value skills are:
- Defining the problem clearly
- Designing systems that solve it securely and efficiently
- Using agents to accelerate execution rather than replacing judgment
The creator’s interpretation of DHH’s “don’t be a loser” message
The creator ultimately suggests DHH’s harsh rhetoric is aimed less at people who like Rails or type code manually, and more at pessimism (“black pilling”) in the face of powerful tools. They frame AI as an accelerator for experimentation and rapid iteration—“a better time to be an idiot with an idea”—illustrated with intentionally absurd startup jokes.
Sponsor segment: CodeRabbit
The creator promotes CodeRabbit as an AI tool for managing the downstream consequences of “cheap code,” especially too many pull requests. They claim it helps triage PRs by ranking them via factors like security risk, review effort, and dependency/blocking relationships, and that teams using it merge PRs four times faster on average.
Transcript
Last week, the legendary developer and creator of Ruby on Rails, David Heinemeier Hansson, DHH, walked into the Rails World Conference in Austin, Texas and made a room of over 1,000 Rails developers break down into tears after telling them that writing Rails or any source code by hand is over. It's no longer economically viable and it's time for you to stop being a loser. >> The black pill is for losers. Don't be a loser. >> DHH has gone completely off the rails and used his keynote to promote AI-generated Rust, which is like the Pope showing up on Easter to talk about the benefits of atheism. And this one's personal for me because Rails was my first framework and launched my career in software development, which ultimately led to me creating this Fireship channel. Watching this keynote was like watching my childhood home get demolished to build a data center. But is DHH right or is he just another hype man with AI psychosis? Well, in today's video, we'll find out by looking at a variety of different skills programmers need to have and determine if those skills are still relevant for software developers in the future. It is September 28th, [music] 2026 and you're watching the Code Report. Let's start with the most vulnerable skill, the keyboard martial arts. It just a couple years ago, it was very in vogue to get good at tools like Neovim. And back in the good [clears throat] old days, memorizing hundreds of keyboard shortcuts and spending hours on a great configuration, it could actually make you write code faster. However, 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 very niche party trick. That being said, DHH himself is a Neovim user and is still a big proponent of command line interfaces, as long as it's not a human using them. In the keynote, he says every app developer should provide a CLI for developers. The only caveat is that command line interfaces are no longer for humans. >> 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 is that code editors and CLI tools will still have a place, but investing a ton of time mastering them is not going to make you a more productive developer. But what about programming frameworks like Ruby on Rails, React JS, Svelte, Angular, Tailwind CSS, and the list goes on. All these frameworks have massive cult-like fan bases. Well, at least they used to anyway. Ruby on Rails explicitly put programmer happiness at the center of its philosophy, and I can vividly remember back in 2008 Rails new felt like using a magic wand, which would generate a full MVC CRUD app in a matter of seconds. But the harsh reality is that developer happiness is dead, and any framework or programming language built around this idea is not going to end well. Like my Horse Tender startup is entirely framework-free. It's built with vanilla JavaScript and Rust on the back end. Frameworks used to provide developer happiness, but now they just get in the way, and in many cases hurt performance. And I'm not the only one. DHH used to be a certified Rust hater. >> THIS IS AN AWFUL, AWFUL, AWFUL PROGRAMMING LANGUAGE when you subject humans to write it. Absolutely inhumane. >> But in the keynote, he shockingly announced that they're rewriting the Hey email app 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. >> With that Rust rewrite, he was able to cut CPU and memory usage by 95% on the server. And that's a hugely important point because the frameworks that will actually survive in the future are the ones that require the fewest amount of tokens and thus save developers money, or the ones that achieve the highest level of performance. Unfortunately, developer happiness is almost a non-factor now. Over the next decade or so, maybe sooner, I think we'll see all frameworks, languages, and runtimes converge down to a single point, like one universal language that can build any type of software you can imagine. A language optimized for tokens that no human needs to understand. And that brings us to the big one, coding or actually writing source code that runs software. DHH claims he went from writing about 30,000 lines of Ruby per year it to now writing about 150,000 lines of code per month using agents. But he's just one random crazy rich dude, so we also asked the audience of 1200 developers how many of them spend a material amount of time each week writing code. Show of hands. Holy that's about five. And if we're to trust that trust me bro poll, that means less than 1% of humans are still writing code by hand. The end of coding is not near, it's already here. I refuse to believe that though, so let me know if you're still writing code by leaving a comment on this video. But something doesn't add up here because if coding really is dead, why haven't there been mass layoffs and why are Silicon Valley companies still hiring developers with six-figure pay packages? Well, the good news in all of this is that writing code or any skill closely tied to mechanical execution was never that valuable to begin with. What's always been far more important is the ability to define a problem, then design a system that can solve that problem securely and efficiently. And AI agents just make that process way faster. And so when DHH told us all to stop being losers, he wasn't calling us losers because we write code by hand. He wasn't calling us losers because we still love Ruby on Rails. He wasn't calling us losers because our Horse Tinder app is failing. He was calling us losers because of our pessimism. Like dude, you have an army of coding robots at your disposal and you're black pilling. There's never been a better time to be an idiot with an idea. Like after Horse Tinder failed to raise a series A, I was able to quickly pivot the idea to Donker, which is like Grinder for gay donkeys. And now it's already expecting its first funding round led by Sam Altman, Peter Thiel, and Tim Cook. But I think Charlie Chaplin says it better than DHH, you'll never find a rainbow if you're looking down. >> YOU THE PEOPLE HAVE THE POWER TO MAKE THIS LIFE FREE AND BEAUTIFUL. >> THE black pill is for losers. Don't be a loser. >> But one thing I'm definitely not black pilled about is Code Rabbit, the sponsor of today's video. AI coding agents have made it so that writing code is basically free now, but the problem is everything after that. The teams now have 200 open pull requests, and GitHub only lets you sort them chronologically. The Code Rabbit triage fixes this by giving you a next best action view for all of your team's PRs across every repo. It ranks each one based on factors like security risk, review effort, and which PRs are blocking other PRs. Then it uses that context to tell you which one to review next, how deep you want to go, and who else on your team should see it. It'll even flag all the PRs that are safe to close, and you can fix failing builds to resolve merge conflicts right from the queue without opening a new tab. The Code Rabbit is the number one most installed AI app on GitHub, and teams using it are merging PRs four times faster on average. Try it out for free today at the link below. This has been The Code Report. Thanks for watching, and I will see you in the next one.
