During the opening keynote at Rails World 2026, Ruby on Rails creator David Heinemeier Hansson (DHH) outlined a significant departure from the framework that has defined his career. While Rails has long been marketed as the ideal stack for small teams building ambitious web applications, DHH revealed that 37signals is moving its flagship product, Hey, to a new architecture. This new approach relies on native applications for each platform and a Rust-based backend, a language DHH previously criticized but now favors for its performance and suitability for LLM-generated code. DHH claims that his personal code output has shifted dramatically, with Ruby now accounting for only 3% of his work, as he embraces a workflow where humans rarely read the code produced by AI agents. This 'no-read' philosophy assumes that LLMs can handle the heavy lifting of development, with humans acting primarily as evaluators of the final output. However, this strategy raises critical questions regarding long-term maintenance and the potential for 'slop'—uncoordinated or low-quality code—to degrade system architecture. Critics argue that DHH’s keynote offered little concrete guidance for the broader Rails community, providing reassurance rather than a clear roadmap for the framework's future. As the industry grapples with the integration of AI into software engineering, the debate continues over whether such tools can truly replace the need for human-readable, maintainable codebases, or if this reliance on AI agents introduces risks that are not yet fully understood.
The article discusses the uncertainty surrounding the Rails ecosystem following DHH's keynote, which is captured by the critical perspective presented in this blog post preview.