korrents
David Heinemeier Hansson

What David Heinemeier Hansson thinks about team size

@dhh · 748 positions · 10 changes of mind · On ppll ↗

Creator of Ruby on Rails, CTO of 37signals, and creator of Omarchy.

David Heinemeier Hansson did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter team size · Newest first

Only David Heinemeier Hansson on team size. See everyone on team size

9 dated positions, 2023 to 2026, in their own words. Our reading of what David Heinemeier Hansson has said — not written or endorsed by them.

  1. I'm worried, and still am, about a team of two, about a team of four, because they will produce software that's competitive with ours because it comes out of the same constraints. And therefore, our threat doesn't come from the behemoth.

    ↗DHH: How to Build a Profitable Company Without Losing Controlyoutube.com 1st of 27 in this recording

  2. Small teams can do incredible things when they embrace their constraints

    ↗Sitting down with Senraworld.hey.com

  3. 12 months earlier
  4. When you're at Netflix scale, when you apply that pattern to a team of 20 programmers working on a code base of half a million lines of code, you're an idiot. You just don't need to turn method invocations into network calls. It is the first rule of distributed programming. Do not distribute your programming.

    ↗DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting | Lex Fridman Podcast #474youtube.com 15th of 36 in this recording

  5. You cannot produce the kind of software that Basecamp is with a team of a thousand people. You will build the kind of software that a thousand people builds. And that's not the same thing at all.

    ↗DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting | Lex Fridman Podcast #474youtube.com 20th of 36 in this recording

  6. design

    our default team size is two. One programmer, one designer, one feature. When you're operating at that level of scale, you don't need sophistication. You don't need advanced methodologies.

    ↗DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting | Lex Fridman Podcast #474youtube.com 21st of 36 in this recording

  7. startupsventure capital

    Because the problem isn't just venture capital, it's other people's money. Once you take other people's money, completely understandably, they want a return and they would prefer to have the largest return possible.

    ↗DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting | Lex Fridman Podcast #474youtube.com 22nd of 36 in this recording

  8. 14 months earlier
  9. The ideal of the one-person framework has never been more relevant

    ↗The last RailsConfworld.hey.com 1st of 2 in this piece

  10. 8 days earlier
  11. Never aspire to a more complicated stack than what your application calls for

    ↗We're moving continuous integration back to developer machinesworld.hey.com

  12. 4 months earlier
  13. the cloud

    The cloud has some advantages, but it's typically not in a reduced operations headcount

    ↗The Big Cloud Exit FAQworld.hey.com 1st of 2 in this piece