ATRIUMsearch → argument graph
Audio · 2020-02-01 · 1h 2m · 6 moments

Story: David Heinemeier Hansson, Software Contrarian

David Heinemeier Hansson talks to Adam about being avoiding a software monoculture. He explains why we should find a programming language that speaks to us, why ergonomics matter and why single page apps and microservices are not for him. "That is the pleasure and privilege of working with the web. No one knows what you built it. It, you could build an in basic, you can build it a Ocaml, you can build in the Haskell, you can build it in whatever Ruby. No one is going to be none the wiser you g ✦ AI generated

Apple Podcasts ↗
GUEST David Heinemeier Hansson

timeline · colored by role

01
Claim◆

The web is uniquely liberating because no one knows what language you built it in, so you can use any programming language you want.

DHH celebrates the web as the only major platform where developers can freely choose any programming language — unlike iOS (Swift) or Android (Java/Kotlin) — because the server-side implementation is invisible to users.

transcript

David Heinemeier Hansson: That is the pleasure and privilege of working with the web. No one knows what you built it in. You could build it in BASIC, you can build it in OCaml, you can build it in Haskell, you can build it in whatever, Ruby. No one is going to be none the wiser. You get to choose, which is really unique advantage of the web as a distribution platform that is very seldomly cherished enough.

extends · 1gives example · 1

02
Mechanism

Ruby on Rails succeeded by combining Java's best architectural ideas with PHP's ease of getting started, using Ruby as the conduit.

DHH explains the three-part formula behind Rails: liberating clever Java framework ideas from their terrible development environment, infusing them with PHP's instant-gratification ease of hello world, and channeling it all through Ruby's expressive, human-centered design.

transcript

David Heinemeier Hansson: So I drew my main experience and influence for Rails from 2 camps. One was Java and the other was PHP. And I thought that Java was simply chock full of clever people who had clever ideas working in an absolutely terrible development environment. So if you could take those clever ideas and liberate them from the environment, you'd be left with some really clever ideas. That was where I drew the other inspiration, which was from PHP, where you literally could do a one-line thing that said, print hello world, and it would show a web page.

explains mechanism · 1extends · 2provides context · 1

03
Claim◆

Ruby's greatest insight was that programmer happiness is the most important design criterion for a programming language.

DHH argues that Ruby's daring bet on prioritizing developer joy over objective metrics like execution speed was revolutionary and deeply human-centered, making programming a pleasurable creative act rather than a purely technical exercise.

transcript

David Heinemeier Hansson: Ruby was incredibly daring, I think, by going out and say, no, the most important thing, the most important design criteria for our programming language is going to be programmer happiness. I mean, what a hippie concept. I showed up here and it felt like Ruby heard me. Ruby saw me. Ruby was sort of speaking to a deeper aspect of my being, almost sort of communicating with my soul.

provides context · 1

04
Claim

Microservices are one of the most damaging trends in web development, and the majestic monolith is far preferable for most teams.

DHH calls microservices an organizational pattern misapplied as a technical one, arguing that turning method calls into network calls introduces enormous complexity that most teams — even those with 50 developers — should not accept. He contrasts it with the 'majestic monolith' that a single person can fully grasp, deploy, and operate.

transcript

David Heinemeier Hansson: I think microservices and the hype around it is probably one of the most damaging trends that has hit web development in the last 10 years. I think very few things have done more damage to the integrity and the productivity of software development teams than the premature application of microservices. I am a staunch and proud supporter of the majestic monolith. This idea that you have a single application that a single person can fully grasp, comprehend, understand, deploy, operate.

05
Claim

Single-page applications combined with microservices represent an absurd level of complexity that would drive him to quit programming.

DHH argues that SPA + microservice stacks are a 'horrifically overused pattern' that makes him nostalgic for the simplicity of J2EE, and that he would rather retire than work in that environment.

transcript

David Heinemeier Hansson: Even if I think that the single page application front end is a horrifically overused pattern, far more so than even microservices, the crimes against programming humanity that have been done in the service of single page applications are far worse. But then, of course, lots of people combine the two. So it's a fleet of microservices serving a single page application, and that's just where I go like completely. Blam, my head explodes.

06
Claim◆

Group chat as the main mode of company communication causes cognitive harm through constant interruptions and should be replaced by asynchronous, full-thought writing.

DHH argues that chat (like Slack) fragments attention, trains people to think in staccato line-by-line fragments instead of cohesive paragraphs, and causes burnout through constant interruption. He advocates for asynchronous writing of full thoughts and structured practices like office hours instead.

transcript

David Heinemeier Hansson: I think actually the introduction of chat as a main source of company communication has probably been the most hurtful introduction in the history of interactive communication tools. It's a terrible way of working. And you don't realize it until you take a step back and look at how your day's spent and how it's broken up and the cognitive harm that happens through interruptions. If you can't seem to get two, three, four hours of uninterrupted time without someone pinging you, it's not good.

provides context · 2

Highlight slides
The Web's Hidden Freedom✦ from: The web is uniquely liberating because no one knows what language you built it in, so you can use any programming language you want.Web vs. Native Platforms✦ from: The web is uniquely liberating because no one knows what language you built it in, so you can use any programming language you want.Programmer Happiness as the Ultimate Design Criterion✦ from: Ruby's greatest insight was that programmer happiness is the most important design criterion for a programming language.Chat has harmed company communication✦ from: Group chat as the main mode of company communication causes cognitive harm through constant interruptions and should be replaced by asynchronous, full-thought writing.The remedy: asynchronous full-thought writing✦ from: Group chat as the main mode of company communication causes cognitive harm through constant interruptions and should be replaced by asynchronous, full-thought writing.
Related episodes
Video · The Cognitive Revolution

Intelligence on the Edge: Liquid AI's Ramin Hasani on the Search for Device-Native Foundation Models

→
Audio · Lex Fridman

#474 – DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting

→
Video · Lenny's Podcast

OpenAI’s Head of Design: This is the best time in history to be a designer | Ian Silber

→