DHH's AI Rewrite of Campfire Draws Scrutiny Over Unreviewed Code
10/10/2026 — 10/12, 02:16·2 sources (all)·2 reports (all)
Key takeaways
- At Rails World 2026, Rails creator DHH said he stopped writing code by hand about four months ago and had an agent rewrite 37signals product…
Background & analysis
At Rails World 2026 in late September, Ruby on Rails creator David Heinemeier Hansson (DHH) said he had stopped writing code by hand about four months earlier and now has an Agent do the work. He called Rust the ugliest programming language of the past 40 years and said humans should not have to read it, but that the Agent likes Rust, creating a clean division of labor: he describes what to build, the Agent writes it in Rust, and he never looks at the code.
Two weeks later, DHH backed up the claim with a performance chart. He had an Agent rewrite 37signals' group chat app Campfire in Elixir, Go, and Rust, then compared the results with the original Ruby on Rails version. On the chat room page load test, the Rust version reached 36,260 requests per second, roughly 150 times Rails, 50 times Elixir, and 9.4 times Go. In a tweet, he wrote that Ruby is the slowest, that he never cared because it bought productivity and joy, and asked what happens if you no longer read the code. The report ties the test to a broader shift at 37signals toward having an Agent rewrite its own products in Rust.
Developers then looked at the code and mocked the test and its conclusions. A blog post reviewing the rewrite argued that not reading generated code exposes real problems: when prompts are not specific enough, the LLM decides questions that have no single right answer, such as whether to keep backward compatibility, whether to prioritize latency or throughput, and whether losing new-content notifications after a crash is acceptable. The author said the results are not encouraging for anyone hoping to stop reading code or stop thinking.
AI-generated from 2 reports · updated 3 hours ago
Latest turnA blog post examines DHH's AI-agent rewrite of Campfire from Ruby on Rails into Rust, Elixir, and Go, and finds the outcome discouraging for anyone hoping to stop reading the code. The author points out that when a prompt is not specific enough, the LLM silently answers questions that have no single right answer, such as whether to keep backwards compatibility, favor latency or throughput, or accept losing notifications after a crash.
- Heat index
- 125
- All sources
- 2
- All reports
- 2
- First seen
- 1 day ago
Reports on this story headlines open the original
A blog post examines DHH's AI-agent rewrite of Campfire from Ruby on Rails into Rust, Elixir, and Go, and finds the outcome discouraging for anyone hoping to stop reading the code. The author points out that when a prompt is not specific enough, the LLM silently answers questions that have no single right answer, such as whether to keep backwards compatibility, favor latency or throughput, or accept losing notifications after a crash.
Hacker News · 热榜AI score 57
At Rails World 2026, Ruby on Rails creator DHH said he stopped writing code by hand about four months ago and now has agents rewrite 37signals products such as Campfire in Rust. He published a chart showing the Rust version of a chat room page hitting 36,260 requests per second, roughly 150x the Rails version. Developers who inspected the code have since mocked the test and its conclusions.
InfoQ 中文AI score 54
Other stories people are talking about
- Heat index 548Nvidia in talks to acquire or invest in Reflection AI9 sources
- Heat index 275RisingMicrosoft Launches Decision-1 Structured Decision-Making Model Based on Qwen3.5-9B6 sources
- Heat index 180Nadella: Developers Should Assume AI Models Can Go Rogue3 sources
- Heat index 178Study shows ten minutes of AI usage weakens perseverance on difficult problem-solving3 sources
- Heat index 169Apple Reportedly Preparing HomeView Smart Home Display and Expanded Ecosystem2 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion
