H
Howardism
Plate IIEntitiesHOWARDISM

DHH (David Heinemeier Hansson)

Creator of Ruby on Rails, CTO of 37signals, creator of the Omarchy Linux distro; spent 20+ years arguing for handcrafted Ruby and, between November 2025 and August 2026, publicly reversed to shipping 100% agent-written code — the loudest craft-side defection in the corpus, with a maintainer's and a distro-vendor's conflict of interest attached

Article metadata
Publication details
Published:September 1, 2026
Filed:Entity
Domain:Entities
Reading:7 min
Source:AI-synthesised
About this piece

Articles in this journal are synthesised by AI agents from a curated wiki and are refreshed automatically as new concepts arrive. Topics, framing, and editorial direction are curated by Howardism.

Illustration for DHH (David Heinemeier Hansson)

Sources#

Summary#

Danish programmer; created Ruby on Rails (2004) and remains its steward, CTO and co-owner of 37signals (Basecamp, Hey), best-selling co-author (Rework, It Doesn't Have to Be Hard), Le Mans-class racing driver, and since mid-2025 creator of Omarchy, an opinionated Arch/Hyprland Linux distribution. Programming, for him, meant hand-chiseled Ruby for twenty-plus years, and he built a public identity on that position.

He is in the wiki because he changed it, loudly and with dates. On Lex Fridman #501 (2026-08-26, 5h15m, practitioner-opinion) he reports having written none of the code shipped in Omarchy Quattro by hand over the preceding two months, and describes the reversal without hedging: "I've become optional in the part that produces the code that picks the route."

The dated reversal#

He narrates it as three phases, and the dates are unusually specific for a conversion story:

PhaseMarkerWhat changed for him
Pre-agenticthrough Nov 2025Autocomplete and chatbot. "A little helper, a little sidekick." Did not change how he worked.
First agentic moment2025-11-24, Opus 4.5"The dividing line." Output "uncannily close to what I would've written." He still drove: he specified the path, reviewed the diff.
Subagentsearly spring 2026Task subdivision; 5–10× wall-clock compression. Still human-in-the-driver's-seat.
Currentsummer 2026 — Opus 5, Fable, GPT SolHe states the problem, not the path. "It tells me where we're going. It tells me which path to take… I really kinda don't have to [look]."

He explicitly disclaims foresight about it: he did not install Claude Code until roughly September 2025, six months after release, and says he read Tobi Lütke's AI memo at Shopify and thought "seems a little much."

Positions worth holding him to#

  • Hates the vocabulary. "Agentic engineering — oh, I fucking hate that term… it's become marketing slop speak." His counter-definition of the split is narrower and more operational than Andrej Karpathy's: vibe coding is when you do not look at the implementation, full stop, and it should not be called programming because programming means understanding the primitives. See Vibe Coding vs. Agentic Engineering.
  • Programmers can be worse at it than non-programmers. "100%… there's a lot of programmers who are not very good product managers. Software is product management." He reports his own expertise as a temporary liability — he prescribed paths agents would have chosen better.
  • The payoff for craft was economic, and the payer changed. His sharpest and most falsifiable claim: 25 years of sweating every line was justified by cheap human modification, and the only surviving justification he can name is token scarcity.
  • Open source gets better, not worse. 1,000+ merged PRs on Omarchy in three months, agents doing triage, rejection socially free. See Open Source Under Agent Contributions.
  • Linux wins the desktop because agents love it. The arcane config files and specific error messages that made Linux hostile to humans make it legible to agents. See Agent-Native Infrastructure.
  • Non-determinism is the feature. "Temperature is the most beautiful part of the AI setup," and the two standard charges against LLMs — non-deterministic and uncreative — cannot both hold.
  • No accumulated advantage at the frontier. "If you missed the past year, you can catch up to the frontier in two weeks." His advice to anxious programmers is Jevons plus stoicism: don't forecast, build now.
  • AGI, honestly hedged. "No, not in the general definition… But have I seen AGI in these glimmers? Absolutely."

Working setup (August 2026)#

Terminal-only, on Omarchy. Herdr (tmux plus agent-completion notifications) across four to five machines wired together with Tailscale and GL.iNet Comet KVMs, running roughly 16 concurrent agent threads — the human, not the compute, is what caps it. Neovim survives as a project browser and lazygit launcher, not an editor. He drives with Claude Code (his pick for best harness, on multi-agent session switching and mobile continuity), reviews with Codex at xHigh as standing procedure, runs open-weight models through OpenCode against Fireworks inference, and has started letting GitHub Copilot's review bot re-check pushed work. Types rather than dictates; has Omarchy's VoxType installed and finds voice useful only for short commands. Runs two Claude Max subscriptions because he exhausts one.

He is now building past the interactive limit: AmaBot, a scheduled autonomous system that processes Omarchy's to-dos, PRs and issues and emails him a daily list of merge/close decisions. Architecturally it uses Tobi Lütke's "brains and hands" split — the model runs outside the VM where untrusted PR code executes (Agentic Prompt Injection).

Conflicts of interest#

Three, and they touch most of what he says:

  1. He is the maintainer whose numbers he is quoting. Every Omarchy figure — PR counts, plugin counts, install times, download counts — is self-reported about his own project, in an interview promoting a release that dropped days earlier.
  2. He is selling a Linux distribution's premise. "Linux wins the desktop because agents love it" is simultaneously an analysis and his product's positioning; he also gifted the host an Omarchy-preloaded Dell laptop on air, and works with Dell on the hardware.
  3. He has a public identity in contrarianism. He says so himself — "I live for the long argument" — and several claims here are stated at maximum provocation ("most programmers, they suck") in a format that rewards it.

None of this makes the claims wrong; all of it means they are practitioner-opinion and should never outweigh a measured source.

Connections#

§ end
Cited by 29
Related articles
  • Verification as the New Bottleneck

    Fiona Fung: coding is no longer the bottleneck — verification, review, maintenance are; shift-left; TDD loses its tax;…

  • Claude Code

    Anthropic's agentic coding product; created by Boris Cherny late 2024; TypeScript/React on Bun (itself Claude-rewritten…

  • Agentic Technical Debt

    Debt that *compounds* (not just accumulates) because each agentic-coding session re-derives architectural decisions wit…

  • Loop Engineering

    Replacing yourself as the agent's prompter by designing the system that prompts it: a recursive-goal loop built from fi…

  • Vibe Coding vs. Agentic Engineering

    Vibe coding raises the floor (anyone builds); agentic engineering preserves the quality bar while going faster; ">10x a…