korrents

What Dex Horthy thinks about software quality

@dex-horthy · 26 positions · 0 changes of mind

Founder of the agent company HumanLayer, author of the 12-factor agents principles, and the engineer who put the name "context engineering" on the practice.

Dex Horthy 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.

5 dated positions, 2026, in their own words. Our reading of what Dex Horthy has said — not written or endorsed by them.

  1. Our readingThe engineering intuition that matters cannot be taught from a textbook — you know bad patterns in software because you have debugged them at three in the morning.

    Their wordsthere's a different kind of intuition that you that you develop over years as a software engineer and uh there's many categories of it but the one I'll I'll call attention to that is like a thing that you cannot teach you cannot do you cannot learn in a textbook. The only way to learn it is like I know bad patterns in software because I have debugged them at three in the morning.

    ↗Context engineering with Dex Horthyyoutube.com 6th of 26 in this recording

    Interesting

  3. Our readingShip for three to six months with nobody reading the code and the codebase gets so bad that starting over is easier than fixing it — we ran a lights-off software factory and shut it down.

    Their wordsWe tried this. We built a lights off software factory in July of 2025 and by November we had shut it down. I think it takes about three to six months of you shipping all the time with nobody reading the code before you realize like, wow, this is getting way worse and it's easier to start over than it is to fix it.

    ↗Context engineering with Dex Horthyyoutube.com 9th of 26 in this recording

    Interesting

  5. Our readingModels will not learn to write maintainable code from today’s benchmarks, because the cost of bad architecture cannot be measured by running the unit tests — it arrives three to six months later.

    Their wordsthe problem with training models on maintainability is like the cost function of bad architecture and bad program design can't be evaluated by running the unit test because it hits you 3 to 6 months later

    ↗Context engineering with Dex Horthyyoutube.com 11th of 26 in this recording

    benchmarksdesignwriting

    Interesting

  7. Our readingAgentic code review raises the floor but cannot be trusted, because the model reading the code is the same model that wrote it, and it will tell you the code is great.

    Their wordsyes it will catch things and it will raise your floor but I don't believe like the model writing the code is the same model reading the code and if you ask a model hey is this code good it's going to be like oh yeah it's great comprehensive it's got unit tests

    ↗Context engineering with Dex Horthyyoutube.com 14th of 26 in this recording

    Interesting

  9. Our readingA team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI.

    Their wordsyou can slow way down and read every PR and read every line of code. Uh, and then you're only going to really get modest benefits from AI because that becomes I I think you should expect maybe 30 to 50% lift in productivity is kind of what I see when we go into teams

    ↗Context engineering with Dex Horthyyoutube.com 16th of 26 in this recording

    Interesting