Last week, the legendary developer and creator of Ruby on Rails, David Hannah Hansen, the 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 foring 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 fire ship 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, a keyboard martial arts. Just a couple years ago, it was very invogue to get good at tools like Neoim. And back in the [clears throat] good old days, memorizing hundreds of keyboard shortcuts and spending hours on a great configuration that 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 and 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 uh 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, ReactJS, spelt, 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 how running Rails New felt like using a magic wand, which would generate a full MVC credit 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. The 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 humanpowered 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 to now writing about 150,000 lines of code per month using agents. But he's just one random crazy rich dude. So he also asked the audience of 1,200 developers how many of them spend a material amount of time each week writing code. >> Show our 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. 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 rap 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 blackpilling. There's never been a better time to be an idiot with an idea. Like after Horset 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 Alman, Peter Teal, and Tim Cook. But I think Charlie Chaplan 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 foring losers. Don't be a loser. But one thing I'm definitely not blackpilled about is Code Rabbit, the sponsor of today's video. The 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. To 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.
Generated algorithmically for Search Engine
Indexing.