DHH’s new way of writing code

Key takeaways

AI tools have shifted from simple autocomplete to sophisticated agents capable of producing high-quality code, but craftsmanship and taste remain essential.
Design and aesthetics in software are critically important, with integrated roles for designers and engineers to craft products that are both beautiful and functional.
The role of senior developers is becoming increasingly valuable as AI accelerates productivity, potentially shifting the demand landscape for software engineers.
Hiring in tech still relies heavily on effort, demonstration of ability, and cultural fit, despite the rise of AI and changing skills requirements.
Maintaining balance, health, and curiosity is vital for long-term success and fulfillment in a rapidly advancing technological world.

Summary

AI’s Impact on Software Development and Craftsmanship

David Heinemeier Hansson (DHH) discusses how AI, initially used for autocomplete, has rapidly evolved to agents capable of producing high-quality code. He emphasizes that despite these advancements, the standards of taste, judgment, and craftsmanship remain crucial. DHH highlights the shift to an agent-first workflow, which has dramatically changed his daily programming activities—moving from manual coding to overseeing AI agents that execute tasks and generate code. This shift is transforming development speeds, allowing even single individuals to build complex, valuable systems rapidly, which further underscores the importance of design, aesthetics, and quality in software. He also warns of the widening gap between senior and junior developers, with AI amplifying the productivity gap and raising questions about the future roles and compensation structures in software engineering.

The Role of Design and Aesthetics in Software Quality

DHH asserts that beauty and function are deeply interconnected in software. He advocates that good taste and aesthetic judgment are vital for building experiences that feel correct and satisfying. At 37signals, designers take on a multifaceted role—shaping what to build, how it functions, and even assisting in implementation. This integrated approach aligns with the philosophy that those who understand the materials—whether code or physical goods—can craft better, more coherent products. He criticizes the decline of native, authentic interfaces and predicts that agent acceleration will empower designers and engineers to produce more refined and authentic user experiences, raising the standards for beauty and craftsmanship in software.

The Changing Landscape of Software Engineering and Hiring in the Age of AI

DHH explores how AI is reshaping the roles of developers, especially highlighting that the most experienced, senior engineers are benefiting the most from AI acceleration by becoming significantly more productive. He describes a possible future where AI agents could handle tasks traditionally performed by humans, including security and deployment at a high level, potentially leading to a reduction in demand for junior developers who are less able to oversee quality control. DHH shares insights on hiring practices at 37signals, emphasizing the importance of effort, demonstration of skill, and cultural fit over mere credentials. He underlines that the best programmers are those who practice diligently and continually improve. The episode concludes with reflections on maintaining health, passion, and curiosity about computers, advocating for a sustainable approach to working and innovating in the rapidly evolving AI-driven landscape.

Show notes

Brought to You By:

• Statsig — ⁠ The unified platform for flags, analytics, experiments, and more.

• Sonar – The makers of SonarQube, the industry standard for automated code review

• WorkOS – Everything you need to make your app enterprise ready.

—

David Heinemeier Hansson (DHH) is the creator of Ruby on Rails and Omarchy, co-founder and CTO of 37signals (maker of Basecamp and HEY), and the author of several books including the best-seller, Remote: Office Not Required, co-written with Jason Fried.

Six months ago, in an episode of the Lex Fridman podcast, David shared how he doesn’t use AI tools to write code: he types out all his code. But things have changed a lot since then.

In this episode, we discuss his approach to building software, how it’s changed in the last six months, and why he now takes an agent-first approach, and how he barely writes any code by hand. We go into how he uses AI agents: which alter how he builds and explores ideas, but also how his standards of quality and craft remain the same.

We also discuss how 37signals thinks about product development, from the role of designers to the importance of aesthetics and taste. David gets into how he sees beauty and functionality as closely linked, and why strong opinions about design lead to better software.

Finally, we look into the uneven impact of AI which amplifies senior engineers while creating challenges for junior developers, and what this may mean for the role of the software engineer.

—

Timestamps

(00:00) Intro

(02:11) Omarchy and Ruby on Rails

(08:25) 37signals overview

(10:12) Launching HEY

(18:38) Building HEY

(22:47) Designers at 37signals

(28:08) The craft of design

(31:52) Why DHH now embraces AI workflows

(39:45) The AI inflection point

(44:23) DHH’s agent-first workflow

(55:09) AI’s impact on junior developers

(1:03:08) Developer experience with AI

(1:16:43) What does AI mean for developers?

(1:23:33) 37signals teams and hiring

(1:38:20) Work-life balance with AI

(1:41:41) Why DHH keeps building

(1:45:24) Closing

—

The Pragmatic Engineer deepdives relevant for this episode:

• Are AI agents actually slowing us down?

• How Claude Code is built

• The future of software engineering with AI: six predictions

• The AI Engineering Stack

• Mitchell Hashimoto’s new way of writing code

• How Linux is built with Greg Kroah-Hartman

—

Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.

Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe