DHH’s new way of writing code
📚 Main Topics
Value of Software Engineering as a Craft
- Emphasis on aesthetics and beauty in software as indicators of correctness.
- The importance of taste and craftsmanship in software development.
Impact of AI on Software Development
- Transition from skepticism to embracing AI tools for coding.
- AI agents are changing how software is built, allowing for more ambitious projects.
- The role of AI in optimizing performance metrics (e.g., P1 requests).
Evolution of 37 Signals and Ruby on Rails
- The journey of 37 Signals from a web design firm to a successful software company.
- The ongoing relevance and renaissance of Ruby on Rails in the context of AI.
Design and User Experience
- Designers at 37 Signals play a crucial role in defining what should be built and how it should work.
- The integration of design and development roles to enhance product quality.
Future of Software Engineering
- Discussion on the potential peak of software engineers as the bottleneck in production.
- The need for software engineers to adapt and develop skills beyond coding, including empathy and communication.
Personal Insights and Work Philosophy
- David's passion for computers and continuous learning.
- The importance of maintaining a balance between work and personal well-being.
✨ Key Takeaways
- Aesthetics in SoftwareBeautiful code is often correct code; aesthetics play a significant role in software engineering.
- AI as a ToolAI tools have evolved to the point where they can significantly enhance productivity and allow developers to tackle projects previously deemed too ambitious.
- Team DynamicsSmaller, focused teams can be more effective than larger teams, especially when leveraging AI.
- Design's RoleDesigners are integral to the development process, influencing both the functionality and aesthetics of software.
- Future SkillsThe landscape of software engineering is changing, and engineers must develop a broader skill set that includes communication and product management.
🧠 Lessons Learned
- Embrace the evolving nature of technology and be open to integrating new tools like AI into your workflow.
- Focus on the quality of work and the importance of design in creating user-friendly software.
- Continuous learning and adaptation are essential for staying relevant in the fast-paced tech industry.
- Maintain a healthy work-life balance to sustain long-term productivity and creativity.
This conversation with David Heinemeier Hansson highlights the transformative impact of AI on software development and the importance of craftsmanship, design, and adaptability in the evolving tech landscape.
Transcript excerpt
0:00 I feel that you very much value software engineering as a craft >> hugely. I mean I think aesthetics is truth. When something is beautiful, it's likely to be correct. I think this is true in mathematics. This is true in physics. This is true in a lot of different domains. >> I wonder if there's a part of AI about the impact of doing work that we would have not done before. >> The number of projects we have tackled internally that we would never even have contemplated starting on or Legion. Jeremy, one of our most agent accelerated people, went like, "We're going to do P1. We're going to optimize
0:30 P1." Literally the fastest 1% of requests, we're going to make them even faster. There's a bit of tension right now is that most of the people I find who are all in, they're working harder than they ever have. And I've seen that with myself now, too. When you can be this effective and impactful on an hour of supervision of these agents, it's really intoxicating. And I need to go, do you know what? This is not like a limited sale. on Lex Freriedman's podcast. You were still rightfully so very skeptical of AI. >> This is a nuance point and maybe it's self- serving, but I don't actually think my opinions have changed. What
🔒 The full, searchable transcript is available with Pro.
Questions & Answers
Common questions about this video
How does David Hayman Hansen view the relationship between aesthetics and correctness in software engineering?
What was David Hansen's initial stance on AI coding tools, and how has his perspective evolved?
How does David Hansen describe the impact of AI on the scope of projects at 37 Signals?
According to David Hansen, what role do designers play at 37 Signals, and how is it different from traditional views?
What does David Hansen say about the future demand for software engineers in the context of AI advancements?
How does David Hansen emphasize the importance of sleep and health for software developers working in an AI-driven environment?
What is David Hansen's motivation for continuing to build and explore in the field of computers and software?
How does David Hansen view the current state of AI adoption in the industry, and what does he predict for the future?
Related summaries
Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again
The creator of Clawd: "I ship code I don't read"
Catholic Priest Interns at PSYCHIATRIC Institute, THEN THIS HAPPENS
Dal Profilo di Funzionamento al PEI -Secondaria 2° g.-
O ASSUNTO PROIBIDO em 2026 na INTERNET: PORQUE NINGUÉM + FALA DISSO?
