korrents
Dex Horthy

Dex Horthy

@dex-horthy · 26 positions · On ppll ↗

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.

6 of Dex Horthy's claims fit 5 mental models. Most often: Feedback loops, Everything decays without maintenance, Leaky abstractions.

Models they name

Their own words name the idea.

Leverage

Tools, code, capital and debt multiply what one person can do, in both directions.

Used by 29 others

A plan that spells out every line of code to change gives you no leverage: it costs as long to read as the pull request, so you end up skimming it and reading the code twice.

  1. Dex Horthy Founder of the agent company HumanLayer And the plan doc, what was bad about it is it didn't give you leverage. The plan was every single line of code that was going to change like in diff blocks and like all the new stuff to write. And so like people would review these plans. We recommended this. We told people to read the plans. We read all our plans. And then eventually I found myself like I just kind of skimmed the plans. Context engineering with Dex Horthyyoutube.com · 15 Jul 2026 · 1:02:53 into the videoAll korrents from this video
    And the plan doc, what was bad about it is it didn't give you leverage. The plan was every single line of code that was going to change like in diff blocks and like all the new stuff to write. And so like people would review these plans. We recommended this. We told people to read the plans. We read all our plans. And then eventually I found myself like I just kind of skimmed the plans.

    Watch from 1:02:53 plays here

    ↗Context engineering with Dex Horthyyoutube.com

    15 Jul 2026 · video · 1h 33m · spoken · machine transcript

Models we see in what they say

Our reading: their claim applies the idea without naming it. The claim is theirs; filing it here is ours.

Feedback loops

Shorten the loop between doing and finding out; whatever a loop rewards is what you become.

Used by 62 others

Models 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.

  1. Dex Horthy Founder of the agent company HumanLayer the 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 · 15 Jul 2026 · 0:43:40 into the videoAll korrents from this video
    the 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

    Watch from 0:43:40 plays here

    ↗Context engineering with Dex Horthyyoutube.com

    15 Jul 2026 · video · 1h 33m · spoken · machine transcript

If you want loop engineering, build one loop at a time and keep them small: every part of the agentic-factory playbook is good advice except the part where you stop reading the code.

  1. Dex Horthy Founder of the agent company HumanLayer if you want to do loops engineering, you should build one loop at a time and you should keep them small and contained. Basically, I think everything except stop reading the code is really good advice. Context engineering with Dex Horthyyoutube.com · 15 Jul 2026 · 0:58:26 into the videoAll korrents from this video
    if you want to do loops engineering, you should build one loop at a time and you should keep them small and contained. Basically, I think everything except stop reading the code is really good advice.

    Watch from 0:58:26 plays here

    ↗Context engineering with Dex Horthyyoutube.com

    15 Jul 2026 · video · 1h 33m · spoken · machine transcript

Everything decays without maintenance

Institutions, code, cities and knowledge run down by default; keeping something alive is work that has to be paid for.

Used by 28 others

Ship 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.

  1. Dex Horthy Founder of the agent company HumanLayer We 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 · 15 Jul 2026 · 0:41:53 into the videoAll korrents from this video
    We 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.

    Watch from 0:41:53 plays here

    ↗Context engineering with Dex Horthyyoutube.com

    15 Jul 2026 · video · 1h 33m · spoken · machine transcript

Leaky abstractions

A shortcut that hides the details works until it doesn't; when it breaks, someone has to know what is underneath.

Used by 8 others

Every abstraction in agentic programming — RAG, memory, agentic history, structured output — is just a different way of passing tokens into a model, and understanding that beats learning any of them.

  1. Dex Horthy Founder of the agent company HumanLayer And at the end of the day, they're all like different ways to pass tokens into a model and ask it to produce usually some structured output. And understanding that is a lot more powerful than trying to learn memory and trying to pick some agent framework off the shelf and some memory framework off the shelf. Context engineering with Dex Horthyyoutube.com · 15 Jul 2026 · 0:21:28 into the videoAll korrents from this video
    And at the end of the day, they're all like different ways to pass tokens into a model and ask it to produce usually some structured output. And understanding that is a lot more powerful than trying to learn memory and trying to pick some agent framework off the shelf and some memory framework off the shelf.

    Watch from 0:21:28 plays here

    ↗Context engineering with Dex Horthyyoutube.com

    15 Jul 2026 · video · 1h 33m · spoken · machine transcript

Positioning

Set up your situation, rules and defaults so the good choice is the easy one, instead of relying on willpower.

Used by 21 others

Harness engineering is raising the floor: optimising the environment a coding agent runs in so that the results of every single turn are as good as possible.

  1. Dex Horthy Founder of the agent company HumanLayer Well, harness engineering just is like how do I raise the floor so that every single turn of this thing, the results are as good as possible. Context engineering with Dex Horthyyoutube.com · 15 Jul 2026 · 0:26:43 into the videoAll korrents from this video
    Well, harness engineering just is like how do I raise the floor so that every single turn of this thing, the results are as good as possible.

    Watch from 0:26:43 plays here

    ↗Context engineering with Dex Horthyyoutube.com

    15 Jul 2026 · video · 1h 33m · spoken · machine transcript