DHH Says AI Lets Small Teams Compete With Software Ecosystems Built by Thousands
David Heinemeier Hansson has a simple pitch for why this is a good moment to be a small team. If an AI agent does a big share of the typing, the headcount gap between you and a platform built by thousands of engineers stops deciding who wins. What’s left is judgement. Which features to build, which to refuse, how the thing should feel when you use it.
He made the case on an a16z podcast released November 20, with general partners Martin Casado and Anish Acharya. The hook is Omarchy, the Arch Linux distribution DHH started in 2025 and has since turned agent-first. The episode runs about 50 minutes and wanders well past Linux: whether a third mobile platform can happen, what counts as superintelligence, big labs against open models, and the return of the pseudonymous hacker.
Ruby on Rails creator David Heinemeier Hansson says AI is giving small teams a chance to compete with software ecosystems built by thousands of developers. In his view, as building software gets faster and cheaper, taste and craft become more important.
DHH joins a16z General Partners Martin Casado and Anish Acharya to explain why he’s building Omarchy, an agent-first Linux distribution. They also cover why Linux is unusually well suited to agents, the importance of open models, the return of individual hackers shaping the future of computing, and more.
00:00 Intro 00:48 From Rails and Basecamp to Linux 03:58 Why AI agents make Linux the better OS 08:17 Can a third mobile platform happen? 16:02 Does taste still matter when AI writes code? 22:57 What counts as superintelligence? 25:58 Big AI labs vs. open source 31:50 DHH’s plan to be bigger than macOS 38:24 Who to follow, and the AI culture war 44:35 The return of the pseudonymous hacker 47:33 90s demo culture and computers with character
YouTube: https://t.co/sLxPWdSG7v
@dhh @martin_casado @illscience
— a16z (@a16z) November 20, 2026
Why Linux suits agents
The Linux argument is practical. An agent works through text: config files, shell commands, logs. Linux exposes almost everything that way. macOS and Windows keep a lot behind GUIs, private APIs and permission dialogs an agent can’t click through cleanly. On an Arch box running Hyprland, the window manager, the status bar, the keybindings and the theme are all plain files. An agent can read them, change them and put them back.
Omarchy leans on that hard. The 4.0 release, Quattro, ships launchers for the common coding agent CLIs (Claude Code, Codex, OpenCode, Copilot CLI and more), downloads none of them until you first run one, and asks you to pick a default at first boot. It also bundles a skill that teaches those agents how Omarchy is put together, so “make the bar smaller and move the clock left” becomes something you can hand off. The plugin marketplace passed 500 plugins in its first week.
For app developers this is the part worth noticing. Linux always charged a tax in knowledge. You had to know where things lived. Once the agent knows where things live, most of that tax disappears, and what remains is what Linux was always good at: it’s open, it’s fast, and no vendor decides what you may install.
Taste becomes the scarce input
The bigger claim is about taste. When writing code is slow and expensive, team size caps what you can ship. When it gets fast and cheap, everybody ships a lot, and most of it is mediocre. Volume stops being a moat. What separates products is the pile of decisions somebody made about what to leave out.
That’s very DHH. Rails was built on convention over configuration, opinionated defaults that spared you a thousand small choices. Basecamp and HEY are narrow on purpose. Omarchy takes its name from omakase, where the chef picks the meal. His bet is that AI makes opinion worth more, because generating options is now free and choosing between them still isn’t.
There’s a fair counterpoint. Judgement doesn’t maintain code. A small team with great taste still owns whatever the agent wrote, and vibe coding works until you have to read the code. Speed on day one turns into review load on day ninety, and small teams have less slack for that, not more.
What app builders can take from it
Whether or not you ever boot Omarchy, a few things carry over. Make your product legible to agents: plain-text config, a real CLI, error messages that say what went wrong and where. Those used to be nice for power users. Now they decide whether somebody’s agent can operate your software on their behalf.
Open models matter for the same reason Omarchy refuses to pick a favourite agent. A product with agents built in shouldn’t hang on one lab’s pricing or policy changes.
And the solo developer is back in the game. One person with a clear point of view and a decent agent setup can ship what used to take a department. Nobody promises users will show up. But if they don’t, headcount won’t be the reason.
DHH says he wants Omarchy to end up bigger than macOS. That’s a long shot. The point underneath it holds well beyond Linux, though: when building gets cheap, knowing what to build is the expensive part.