Rails Creator DHH Abandons Hand-Written Code for AI-Generated Rust

DHH has gone completely off the rails... — Fireship

Fireship

Writing code by hand has become economically obsolete as autonomous agents generating low-level Rust slash infrastructure costs by 95%, shifting software engineering value from syntax creation to system architecture.

AI-assisted summary of DHH has gone completely off the rails... — original source. Check the original for full context.

Source published:

Key ideas

  • At Rails World, Ruby on Rails creator DHH declared hand-written source code economically obsolete, urging engineers to embrace agentic workflows over manual coding. (0:00)
  • Basecamp's rewrite of the HEY email backend into AI-generated Rust slashed server CPU and memory consumption by 95%, underscoring a shift toward machine-first performance over human ergonomics. (1:10)
  • DHH reported expanding his output from 30,000 lines of Ruby per year to 150,000 lines per month using agents, while a poll of 1,200 Rails World attendees showed fewer than 1% still write code manually. (3:55)
  • As the marginal cost of creating code drops to zero, software engineering bottlenecks have shifted downstream to pull request triage, dependency management, and code review. (5:45)

Detailed notes

## Background Published by Fireship on YouTube on September 28, 2026, this episode of The Code Report reacts to David Heinemeier Hansson (DHH) declaring to 1,200 Rails developers that writing code by hand is over. The video explores which developer skills are still worth having in an agent-driven world and features a showcase of CodeRabbit Triage.

## TL;DR At the Rails World conference, Ruby on Rails creator DHH delivered a startling keynote proclaiming that writing code by hand is economically obsolete, advocating instead for AI-generated Rust to achieve massive efficiency gains. This paradigm shift diminishes traditional 'keyboard martial arts' and human-centric framework ergonomics, redirecting value toward problem definition, system architecture, and token-optimized execution. With agents making syntax generation essentially free, the industry's primary operational bottleneck has shifted downstream toward reviewing, testing, and triaging massive pull request backlogs.

## Atmosphere & style The presentation is trademark Fireship: fast-paced, satirical, and irreverent, balancing genuine career nostalgia with deadpan comedic absurdity. It opens with dramatic, mock-tragic shock—likening DHH's stance to bulldozing a childhood home or the Pope preaching atheism—before peppering the narrative with ridiculous fake startup pitches like 'Donker.' Beneath the chaotic humor and existential anxiety about the death of developer happiness lies a spirited, pragmatic case for technological optimism.

## Bulletin - [00:00](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=0s) At Rails World, Ruby on Rails creator DHH declared hand-written source code economically obsolete, urging engineers to embrace agentic workflows over manual coding. - [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) Basecamp's rewrite of the HEY email backend into AI-generated Rust slashed server CPU and memory consumption by 95%, underscoring a shift toward machine-first performance over human ergonomics. - [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) DHH reported expanding his output from 30,000 lines of Ruby per year to 150,000 lines per month using agents, while a poll of 1,200 Rails World attendees showed fewer than 1% still write code manually. - [05:45](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=345s) As the marginal cost of creating code drops to zero, software engineering bottlenecks have shifted downstream to pull request triage, dependency management, and code review.

## Key takeaways - [00:00](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=0s) DHH announced to over 1,000 developers at Rails World that writing application code by hand is no longer economically viable. - [00:00](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=0s) Rejecting tech pessimism, DHH declared that 'the black pill is for losers,' urging engineers to adapt to AI-driven workflows rather than mourn legacy practices. - [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) Mastery over complex editor configurations and terminal keybindings no longer grants a meaningful productivity edge in an agent-driven development cycle. - [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) Command-line interfaces remain essential, but their primary audience has shifted from human operators to autonomous software agents. - [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) The industry's historical emphasis on 'developer happiness' is giving way to designs optimized for AI token efficiency and raw runtime execution speed. - [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) Despite previously calling Rust inhumane for human coders, DHH endorsed AI-generated Rust after using it to reduce HEY's infrastructure footprint by 95%. - [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) DHH escalated his personal coding output from roughly 30,000 lines of Ruby per year to 150,000 lines of agent-generated code per month. - [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) An informal poll of 1,200 Rails World attendees revealed only about five engineers still spend significant portions of their workweek hand-coding. - [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) Core engineering value resides in architecture, problem formulation, and operational security rather than syntax authoring. - [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) On-demand agentic tooling has dramatically lowered execution barriers, giving a distinct advantage to optimistic builders who iterate quickly. - [05:45](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=345s) Mass AI code generation has created an acute operational crisis in pull request reviews, turning review backlogs into the primary engineering constraint. - [05:45](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=345s) Modern developer tooling is increasingly shifting toward risk-weighted triage and automated review prioritization to handle massive surges in agent-created pull requests.

## Detailed walkthrough ### [00:00](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=0s) DHH’s Bombshell at Rails World and the AI Rust Heresy

At the Rails World conference in Austin, Texas, Ruby on Rails creator David Heinemeier Hansson (DHH) took the stage in front of over a thousand Rails developers and dropped an existential bomb: writing Rails or any source code by hand is effectively dead, no longer economically viable, and anyone clinging to the past needs to move on. DHH punctuated this message with a stern warning against tech pessimism: "The black pill is for losers. Don't be a loser." Instead of championing the beloved framework he authored, DHH used his keynote to advocate for AI-generated Rust. For the audience and the broader developer ecosystem, this was the spiritual equivalent of the Pope showing up to Easter Mass to preach the virtues of atheism.

For the host of The Code Report, the keynote struck an intensely personal nerve. Ruby on Rails was the foundational framework that originally launched his software engineering career and directly led to the birth of the Fireship YouTube channel. Watching DHH abandon manual Rails coding felt like watching his own childhood home get bulldozed just to make room for a giant data center. The keynote forced an immediate reckoning with whether DHH has genuinely diagnosed the structural future of software engineering or simply fallen victim to extreme "AI psychosis."

- **Setting:** Rails World Conference in Austin, Texas, with over 1,000 developers in attendance. - **DHH's Thesis:** Writing application source code by hand is economically obsolete and impossible to justify commercially. - **Core Catchphrase:** "The black pill is for losers. Don't be a loser." - **Host's Career Connection:** Rails was the host's first professional framework, providing the technical runway that eventually produced the Fireship platform.

---

[01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) The Death of Keyboard Martial Arts and Developer Happiness

The report examines the first skill rendered obsolete in this new era: "keyboard martial arts." Only a few years ago, mastery of tools like Neovim, memorizing hundreds of keybindings, and tweaking elaborate text editor configurations could tangibly accelerate a developer's output. But when an AI agent handles the overwhelming majority of code edits, being able to wipe out the contents of a pair of parentheses in three rapid keystrokes without reaching for a mouse has been downgraded from a superpower to a niche party trick. While DHH remains an avid Neovim user and still insists on the primacy of the command-line interface (CLI), he explicitly argued that CLIs are no longer intended for human eyes. During his keynote, DHH demanded: "It is your obligation to deliver those CLIs by next Friday so I can use your application without actually ever having to touch it." Mastering editors and terminal mechanics no longer provides a competitive edge in developer productivity.

```mermaid flowchart TD accTitle: Paradigm Shift in Software Engineering accDescr: Comparison of traditional human-centric development versus modern agent-driven development. subgraph Traditional["Traditional Paradigm (Human Happiness)"] A["Human Programmer"] -->|"Handcrafted edits"| B["Keyboard Mastery & IDEs"] B -->|"Framework ergonomics"| C["Ruby on Rails / React"] C -->|"Costly execution"| D["High CPU / Memory Footprint"] end subgraph Agentic["Emerging Paradigm (Agentic Efficiency)"] E["High-Level Problem Spec"] -->|"Prompts & Agents"| F["Agentic CLI Interfaces"] F -->|"AI Generation"| G["Token-Optimized Rust"] G -->|"Machine execution"| H["95% Resource Reduction"] end ```

The erosion of human craft extends directly into web frameworks such as Ruby on Rails, React, Svelte, Angular, and Tailwind CSS. Rails rose to dominance on the promise of prioritizing developer happiness—a feeling epitomized back in 2008 when running `rails new` generated a complete MVC CRUD application within seconds like a magic wand. But developer happiness as an engineering target is now practically dead. Highlighting this shift, the host notes that his own startup, Horse Tinder, bypassed modern frameworks altogether in favor of vanilla JavaScript and a backend written in Rust.

DHH's transformation on this topic is particularly striking. He was once a vocal critic of Rust, famously describing it in the past as "AN AWFUL, AWFUL, AWFUL PROGRAMMING LANGUAGE when you subject humans to write it. Absolutely inhumane." Yet in his keynote, DHH revealed that Basecamp is actively rewriting the backend of their email service, HEY, not with human-crafted Ruby, but using fully AI-generated Rust: "Rust is amazing if you never, ever, ever have to look at it yourself." The technical payoff was undeniable: the Rust rewrite slashed server CPU and memory consumption by 95%. Going forward, the frameworks that survive will not be the ones that spark joy in human coders; they will be the ones that minimize AI token consumption and maximize runtime raw performance. Eventually, the entire landscape of distinct frameworks, languages, and runtimes may collapse into a single universal, token-efficient language designed exclusively for machines.

- **Editor Mastery:** Spending hundreds of hours perfecting Neovim setups or terminal shortcuts yields negligible returns when agents generate and edit code. - **Agent-First CLIs:** CLIs remain mandatory, but their primary consumers are now autonomous agents executing programmatic workflows rather than human operators. - **The End of Developer Happiness:** Frameworks optimized around pleasant syntax and developer ergonomics are yielding to low-level, high-efficiency systems. - **The HEY Email Rewrite:** Rewriting the HEY email application from Ruby on Rails to AI-generated Rust yielded an immediate 95% reduction in CPU and memory usage.

---

[03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) The Death of Hand-Written Code and Why the Optimists Win

Turning to the act of writing software by hand, DHH shared staggering personal productivity metrics: he went from writing around 30,000 lines of Ruby code per year to generating roughly 150,000 lines of code every single month using automated agents. To test whether this was an isolated anomaly, DHH conducted a live show-of-hands poll across the 1,200 attendees at Rails World, asking how many still spent a material portion of their week hand-coding. Only about five people in the entire auditorium raised their hands, implying that less than 1% of the audience still writes code manually.

Despite hand-written code disappearing, the industry has not seen the total collapse of engineering employment, nor have Silicon Valley firms stopped offering lucrative six-figure salaries. The explanation is simple: mechanical syntax generation was never the truly valuable part of software engineering. The irreplaceable skill has always been problem definition, system architecture, security planning, and operational efficiency—tasks that agents dramatically accelerate rather than replace.

DHH's warning against being a "loser" was not an insult aimed at developers who cherish Rails, write code manually, or struggle with a failing startup. Rather, it was a critique of cynicism and defeatism. With an on-demand army of robotic coding agents at everyone's disposal, "there’s never been a better time to be an idiot with an idea." The host illustrates this with a comedic anecdote: when his startup Horse Tinder failed to raise a Series A funding round, he pivoted immediately to "Donker"—pitched as "Grindr for gay donkeys"—which is now preparing for an initial investment round backed by Sam Altman, Peter Thiel, and Tim Cook. Quoting Charlie Chaplin's famous line, "you'll never find a rainbow if you're looking down," the video emphasizes that optimism and rapid execution are the real competitive differentiators.

- **DHH's Output Jump:** Increased from ~30,000 lines of Ruby annually to ~150,000 lines of agent-generated code per month. - **Rails World Poll:** Out of 1,200 professional developers, only around 5 developers still spend meaningful time writing code manually. - **Real Value in Engineering:** Translating ambiguous business problems into secure, high-performance architecture rather than typing syntax. - **The Startup Pivot Joke:** Transitioning from the failed Horse Tinder to Donker ("Grindr for gay donkeys"), jokingly targeting capital from Sam Altman, Peter Thiel, and Tim Cook.

---

[05:45](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=345s) The Post-Coding Bottleneck: CodeRabbit Triage

While generative agents have effectively driven the marginal cost of creating code down to zero, they have simultaneously created an acute operational bottleneck on everything that follows. Development teams are routinely swamped under backlogs of 200 open pull requests, while standard GitHub views only allow sorting by chronological order. This problem introduces CodeRabbit, the sponsor of the episode, which tackles PR overload using automated triage.

CodeRabbit Triage delivers a "next best action" dashboard across an organization's repositories, ranking pending PRs by risk profile, review effort, and blocking dependencies. It guides engineers on which PRs to inspect first, recommends how deep the review needs to go, identifies necessary teammates, and flags PRs that can be closed safely. Developers can even fix failing builds and resolve merge conflicts directly from the review queue without having to switch tabs. Holding the status of the number-one installed AI application on GitHub, CodeRabbit helps teams merge pull requests up to four times faster.

- **The New Bottleneck:** Writing code is essentially free, but reviewing, vetting, and managing pull requests has become an overwhelming operational hurdle. - **CodeRabbit Triage Capabilities:** Evaluates pull requests across all team repositories, scoring them by security risk, review complexity, and blocking status. - **Queue Management:** Enables engineers to fix failing CI builds and clear merge conflicts directly within the interface without opening extra browser tabs. - **Adoption Metric:** Holds the spot as the #1 most installed AI application on GitHub, driving average merge speeds up by 4x.

## Notable quotes > [00:00](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=0s) The black pill is for losers. Don't be a loser. — David Heinemeier Hansson (DHH)

> [00:00](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=0s) AI psychosis — Host

> [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) keyboard martial arts — Host

> [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) It is your obligation to deliver those CLIs by next Friday so I can use your application without actually ever having to touch it. — David Heinemeier Hansson (DHH)

> [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) AN AWFUL, AWFUL, AWFUL PROGRAMMING LANGUAGE when you subject humans to write it. Absolutely inhumane. — David Heinemeier Hansson (DHH)

> [01:10](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=70s) Rust is amazing if you never, ever, ever have to look at it yourself. — David Heinemeier Hansson (DHH)

> [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) there’s never been a better time to be an idiot with an idea. — Host

> [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) Grindr for gay donkeys — Host

> [03:55](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=235s) you'll never find a rainbow if you're looking down — Charlie Chaplin

> [05:45](https://www.youtube.com/watch?v=OuNKBjuV7A4&t=345s) next best action

## Mentioned David Heinemeier Hansson (DHH), Ruby on Rails, Rust, Ruby, Rails World, The Code Report, Fireship, Neovim, Basecamp, HEY, React, Svelte, Angular, Tailwind CSS, JavaScript, Horse Tinder, Donker, Sam Altman, Peter Thiel, Tim Cook, Charlie Chaplin, CodeRabbit, GitHub

## Video description CodeRabbit Triage prioritizes all your team's pull requests for you. Try it free: https://coderabbit.link/fireship-014

DHH told 1,200 Rails developers that writing code by hand is over... so let's find out which programming skills are actually still worth having.

Want more Fireship?

🗞️ Newsletter: https://bytes.dev 🧠 Courses: https://fireship.dev

[Source](https://www.youtube.com/watch?v=OuNKBjuV7A4)

中文简报

Rails创始人DHH放弃手写代码,转向AI生成的Rust 随着自主智能体生成底层Rust将基础设施成本削减95%,手动编写代码在经济层面上已显过时,软件工程的价值正从语法编写转向系统架构。 在Rails World大会上,Ruby on Rails创始人DHH发表了令人瞩目的主题演讲,宣称手动编写代码在经济层面上已被淘汰,并主张采用AI生成的Rust来实现巨大的效率提升。这一范式转变削弱了传统的“键盘武术”和以人为本的框架易用性,将价值重心重新导向问题定义、系统架构以及面向Token优化的执行。随着智能体使语法生成几乎零成本,行业的主要运营瓶颈已向下游转移至审查、测试以及处理积压的大量拉取请求(Pull Request)。 在Rails World大会上,Ruby on Rails创始人DHH宣称手写源代码在经济层面上已被淘汰,呼吁工程师拥抱智能体工作流而非手动编码。 (0:00) Basecamp利用AI生成的Rust重写了HEY电子邮件后端,将服务器CPU和内存消耗削减了95%,凸显了从人类易用性转向机器优先性能的转变。 (1:10) DHH透露,在使用智能体后,他的产出从每年3万行Ruby跃升至每月15万行;而对1200名Rails World参会者的调查显示,仍手动编写代码的人不足1%。 (3:55) 随着编写代码的边际成本趋近于零,软件工程的瓶颈已向下游转移至拉取请求分类筛选、依赖管理以及代码审查。 (5:45)

Reading summary

At the Rails World conference, Ruby on Rails creator David Heinemeier Hansson (DHH) declared that writing source code by hand is economically obsolete, urging engineers to embrace AI generation and machine-level performance over traditional developer ergonomics. The Obsolescence of Manual Coding and Tooling Mastery (0:00) During his keynote before more than 1,000 attendees in Austin, Texas, DHH argued that manually writing application source code can no longer be justified commercially. In this emerging paradigm, technical skills previously valued for productivity—such as advanced text editor configurations, complex Neovim keybindings, and rapid manual text manipulation—have been reduced from engineering superpowers to minor party tricks. Because autonomous agents now handle the bulk of code authoring and modifications, keyboard-centric speed provides negligible competitive advantage. This shift also changes the nature of developer interfaces. While DHH maintained that the command-line interface (CLI) remains essential, he argued that CLIs should now be designed primarily for autonomous AI agents rather than human operators. DHH stated that developers now have an obligation to provide agent-accessible CLIs so applications can be orchestrated programmatically without direct human touch. Prioritizing Machine Efficiency Over Developer Happiness (1:10) For decades, frameworks like Ruby on Rails gained popularity by optimizing for developer ergonomics and the subjective feeling of programming joy. According to DHH and the host, this focus is being replaced by architectural goals that minimize AI token consumption and maximize execution performance. Software frameworks of the future are expected to cater to autonomous models rather than human readability, potentially collapsing varied runtime ecosystems into unified, token-efficient formats designed strictly for machines. This transition is illustrated by DHH’s reversal on the Rust programming language. Despite previously denouncing Rust as an inhumane language when humans are subjected to writing it, DHH reported that Basecamp is actively rewriting the backend of its email service, HEY, in AI-generated Rust. Because human engineers do not need to read or maintain the raw syntax, Basecamp achieved a 95% reduction in CPU and memory usage, demonstrating the operational incentive to substitute human-friendly frameworks with low-level, machine-optimized code. Shifting Engineering Value and Tech Optimism (3:55) DHH reported that his personal output increased from roughly 30,000 lines of Ruby per year to approximately 150,000 lines of agent-generated code per month. A live poll conducted during the keynote revealed that among 1,200 Rails World attendees, only about five raised their hands to indicate they still spend substantial time manually writing code, suggesting that less than 1% of the audience remains focused on manual syntax creation. Despite the reduction in manual typing, the host observed that engineering roles and compensation have not collapsed. The core value of software engineering remains anchored in higher-level responsibilities: translating ambiguous business requirements into system architecture, managing security, and ensuring operational performance. DHH condemned defeatist attitudes toward AI—stating that 'the black pill is for losers'—and maintained that the dramatic drop in implementation friction creates historic opportunities for builders willing to experiment and deploy quickly. The Emerging Bottleneck in Pull Request Review (5:45) As automated agents drive the marginal cost of code creation to near zero, the primary development bottleneck has shifted from authoring software to triaging and reviewing code. Development teams are increasingly swamped by vast queues of open pull requests, where traditional chronological repository views fail to address the volume of incoming changes. This operational challenge has spurred adoption of automated triage systems, such as CodeRabbit Triage. By evaluating pull requests across codebases, analyzing risk profiles, estimating required review effort, and surfacing blocking dependencies, automated triage tools attempt to resolve merge conflicts and manage CI failures directly, helping development teams maintain throughput in high-volume, agent-generated environments. While AI agents have drastically lowered the cost of generating code and enabled massive runtime performance gains, they have displaced human developer happiness as a primary design goal and transferred engineering strain to architectural oversight, triage, and review.

Source quotes

[0:00] David Heinemeier Hansson (DHH): The black pill is for losers. Don't be a loser. [0:00] Host: AI psychosis [1:10] Host: keyboard martial arts [1:10] David Heinemeier Hansson (DHH): It is your obligation to deliver those CLIs by next Friday so I can use your application without actually ever having to touch it. [1:10] David Heinemeier Hansson (DHH): AN AWFUL, AWFUL, AWFUL PROGRAMMING LANGUAGE when you subject humans to write it. Absolutely inhumane. [1:10] David Heinemeier Hansson (DHH): Rust is amazing if you never, ever, ever have to look at it yourself. [3:55] Host: there’s never been a better time to be an idiot with an idea. [3:55] Host: Grindr for gay donkeys [3:55] Charlie Chaplin: you'll never find a rainbow if you're looking down [5:45] next best action

Original transcript

[0:00] Last week, the legendary developer and [0:02] creator of Ruby on Rails, David [0:04] Heinemeier Hansson, DHH, walked into the [0:06] Rails World Conference in Austin, Texas [0:08] and made a room of over 1,000 Rails [0:10] developers break down into tears after [0:13] telling them that writing Rails or any [0:15] source code by hand is over. It's no [0:17] longer economically viable and it's time [0:19] for you to stop being a loser. [0:21] >> The black pill is for losers. [0:23] Don't be a loser. [0:32] >> DHH has gone completely off the rails [0:35] and used his keynote to promote [0:36] AI-generated Rust, which is like the [0:38] Pope showing up on Easter to talk about [0:40] the benefits of atheism. And this one's [0:42] personal for me because Rails was my [0:44] first framework and launched my career [0:45] in software development, which [0:47] ultimately led to me creating this [0:48] Fireship channel. Watching this keynote [0:50] was like watching my childhood home get [0:52] demolished to build a data center. But [0:54] is DHH right or is he just another hype [0:56] man with AI psychosis? Well, in today's [0:58] video, we'll find out by looking at a [1:00] variety of different skills programmers [1:01] need to have and determine if those [1:03] skills are still relevant for software [1:05] developers in the future. It is [1:06] September 28th, [music] 2026 and you're [1:08] watching the Code Report. Let's start [1:10] with the most vulnerable skill, the [1:11] keyboard martial arts. It just a couple [1:13] years ago, it was very in vogue to get [1:15] good at tools like Neovim. And back in [1:17] the good [clears throat] old days, [1:18] memorizing hundreds of keyboard [1:20] shortcuts and spending hours on a great [1:22] configuration, it could actually make [1:23] you write code faster. However, if an [1:25] agent is making most of your code edits [1:27] now, being able to delete the contents [1:29] of parentheses in three keystrokes [1:30] without touching your mouse is becoming [1:32] a very niche party trick. That being [1:34] said, DHH himself is a Neovim user and [1:37] is still a big proponent of command line [1:39] interfaces, as long as it's not a human [1:41] using them. In the keynote, he says [1:43] every app developer should provide a CLI [1:45] for developers. The only caveat is that [1:47] command line interfaces are no longer [1:48] for humans. [1:49] >> It is your obligation [1:52] to deliver those [1:54] CLIs by next Friday so I can [1:57] use your application [1:59] without actually ever having to touch [2:00] it. [2:01] >> The bottom line is that code editors and [2:02] CLI tools will still have a place, but [2:04] investing a ton of time mastering them [2:06] is not going to make you a more [2:08] productive developer. But what about [2:09] programming frameworks like Ruby on [2:11] Rails, React JS, Svelte, Angular, [2:14] Tailwind CSS, and the list goes on. All [2:16] these frameworks have massive cult-like [2:18] fan bases. Well, at least they used to [2:20] anyway. Ruby on Rails explicitly put [2:23] programmer happiness at the center of [2:24] its philosophy, and I can vividly [2:26] remember back in 2008 Rails new felt [2:29] like using a magic wand, which would [2:31] generate a full MVC CRUD app in a matter [2:33] of seconds. But the harsh reality is [2:35] that developer happiness is dead, and [2:37] any framework or programming language [2:39] built around this idea is not going to [2:41] end well. Like my Horse Tender startup [2:42] is entirely framework-free. It's built [2:44] with vanilla JavaScript and Rust on the [2:46] back end. Frameworks used to provide [2:48] developer happiness, but now they just [2:50] get in the way, and in many cases hurt [2:51] performance. And I'm not the only one. [2:53] DHH used to be a certified Rust hater. [2:56] >> THIS IS AN AWFUL, AWFUL, AWFUL [2:59] PROGRAMMING LANGUAGE when you subject [3:01] humans to write it. [3:03] Absolutely inhumane. [3:05] >> But in the keynote, he shockingly [3:07] announced that they're rewriting the Hey [3:09] email app not with human-powered Ruby on [3:11] Rails, but with pure AI-generated Rust. [3:14] >> Rust is amazing [3:17] if you never, ever, ever have to look at [3:22] it yourself. [3:22] >> With that Rust rewrite, he was able to [3:24] cut CPU and memory usage by 95% on the [3:27] server. And that's a hugely important [3:29] point because the frameworks that will [3:30] actually survive in the future are the [3:32] ones that require the fewest amount of [3:33] tokens and thus save developers money, [3:36] or the ones that achieve the highest [3:37] level of performance. Unfortunately, [3:39] developer happiness is almost a [3:41] non-factor now. Over the next decade or [3:42] so, maybe sooner, I think we'll see all [3:45] frameworks, languages, and runtimes [3:46] converge down to a single point, like [3:48] one universal language that can build [3:50] any type of software you can imagine. A [3:52] language optimized for tokens that no [3:54] human needs to understand. And that [3:55] brings us to the big one, coding or [3:57] actually writing source code that runs [3:59] software. DHH claims he went from [4:01] writing about 30,000 lines of Ruby per [4:03] year it to now writing about 150,000 [4:06] lines of code per month using agents. [4:08] But he's just one random crazy rich [4:10] dude, so we also asked the audience of [4:12] 1200 developers how many of them spend a [4:14] material amount of time each week [4:16] writing code. Show of hands. [4:18] Holy that's about five. And if we're to [4:21] trust that trust me bro poll, that means [4:23] less than 1% of humans are still writing [4:26] code by hand. The end of coding is not [4:28] near, it's already here. I refuse to [4:30] believe that though, so let me know if [4:31] you're still writing code by leaving a [4:33] comment on this video. But something [4:34] doesn't add up here because if coding [4:36] really is dead, why haven't there been [4:37] mass layoffs and why are Silicon Valley [4:39] companies still hiring developers with [4:41] six-figure pay packages? Well, the good [4:43] news in all of this is that writing code [4:45] or any skill closely tied to mechanical [4:47] execution was never that valuable to [4:49] begin with. What's always been far more [4:51] important is the ability to define a [4:53] problem, then design a system that can [4:54] solve that problem securely and [4:56] efficiently. And AI agents just make [4:58] that process way faster. And so when DHH [5:00] told us all to stop being losers, he [5:03] wasn't calling us losers because we [5:04] write code by hand. He wasn't calling us [5:07] losers because we still love Ruby on [5:08] Rails. He wasn't calling us losers [5:10] because our Horse Tinder app is failing. [5:12] He was calling us losers because of our [5:14] pessimism. Like dude, you have an army [5:16] of coding robots at your disposal and [5:17] you're black pilling. There's never been [5:19] a better time to be an idiot with an [5:20] idea. Like after Horse Tinder failed to [5:22] raise a series A, I was able to quickly [5:24] pivot the idea to Donker, which is like [5:26] Grinder for gay donkeys. And now it's [5:28] already expecting its first funding [5:29] round led by Sam Altman, Peter Thiel, [5:32] and Tim Cook. But I think Charlie [5:33] Chaplin says it better than DHH, you'll [5:35] never find a rainbow if you're looking [5:37] down. [5:38] >> YOU THE PEOPLE HAVE THE POWER TO MAKE [5:39] THIS LIFE FREE AND BEAUTIFUL. [5:41] >> THE black pill is for [5:43] losers. Don't be a loser. [5:45] >> But one thing I'm definitely not black [5:47] pilled about is Code Rabbit, the sponsor [5:49] of today's video. AI coding agents have [5:51] made it so that writing code is [5:52] basically free now, but the problem is [5:55] everything after that. The teams now [5:56] have 200 open pull requests, and GitHub [5:59] only lets you sort them chronologically. [6:01] The Code Rabbit triage fixes this by [6:03] giving you a next best action view for [6:05] all of your team's PRs across every [6:07] repo. It ranks each one based on factors [6:10] like security risk, review effort, and [6:12] which PRs are blocking other PRs. Then [6:14] it uses that context to tell you which [6:16] one to review next, how deep you want to [6:18] go, and who else on your team should see [6:20] it. It'll even flag all the PRs that are [6:22] safe to close, and you can fix failing [6:24] builds to resolve merge conflicts right [6:26] from the queue without opening a new [6:27] tab. The Code Rabbit is the number one [6:29] most installed AI app on GitHub, and [6:31] teams using it are merging PRs four [6:33] times faster on average. Try it out for [6:36] free today at the link below. This has [6:37] been The Code Report. Thanks for [6:39] watching, and I will see you in the next [6:40] one.