Dex Horthy on Why AI Code Is Still Garbage With a Perfect Spec
By Matt Cullerton, founder of Mavric and Apso
Dex Horthy, CEO of HumanLayer, says you can hand a coding model a strong architecture doc, watch it follow the doc exactly, and still get code full of leaky abstractions and tramp data. The quote is real and comes from a longer podcast episode. The clip stops before his explanation, which is that both defects pass every test and satisfy every spec, so nothing in the pipeline catches them.
Where the clip comes from
A TikTok from @wordman.dev, the account of Jan-Niklas Wortmann, posts a short excerpt of Horthy saying "somehow the code is still garbage." Wortmann hosts The Weekly Dev's Brew and works as a JetBrains developer advocate for JavaScript and TypeScript.
The source is episode 21 of the show, "Dex Horthy - What Actually Gets You 2-3x With AI Coding", published 13 August 2026. The published transcript contains the clip's lines word for word, including "you can give it a really good architecture doc and the model can follow it to the letter," "there's still like leaky abstractions, tramp data everywhere," and "Mermaid charts, here's the modules, here's the new endpoints."
The on-screen header in the TikTok reads "The code is still garbage." The spoken line is "But somehow the code is still garbage." The header drops "But somehow," which is the part that carries his surprise.
Who is Dex Horthy
Horthy is co-founder and CEO of HumanLayer, a Y Combinator Fall 2024 company founded in 2023. He wrote 12-Factor Agents, whose Factor 3 is "Own your context window." Before HumanLayer he spent seven years at Replicated, and he started programming at NASA's Jet Propulsion Laboratory.
That background matters here. The author of a context-engineering framework is arguing that good context alone does not produce good code.
What is tramp data?
Tramp data is a catalogued code smell. DevIQ defines it as a piece of data that travels through several method calls as a parameter, where the intermediate methods neither use it nor care about it and only pass it along to the next call. Luzkan's code smell catalogue attributes the term to Steve Smith's 2013 course "Refactoring Fundamentals" and traces the idea to Steve McConnell's Code Complete (1993).
The phrase sounds like a transcription error. The video's own burned-in captions also render it as "tramp data," so it is what he said.
What is a leaky abstraction?
The term comes from Joel Spolsky's essay The Law of Leaky Abstractions, published 11 November 2002. Its central claim is that all non-trivial abstractions are to some degree leaky. In practice a leaky abstraction is a module boundary that forces callers to know about the details it was supposed to hide.
Why does a perfect spec still produce bad code?
Both defects compile and pass unit tests. A module boundary that leaks and a parameter threaded through four functions that ignore it both satisfy an architecture doc that lists modules and endpoints. The doc specifies structure, and the model already satisfies structure. The defects that remain are the ones nothing in the pipeline measures.
Horthy makes this argument in more detail on The Pragmatic Engineer. He says current coding models are likely trained in a way that makes codebases worse over time, because benchmarks such as SWE-bench reward reproducing known fixes and cannot score a bad architectural decision. His phrasing: "the cost function of bad architecture and bad program design cannot be evaluated by running a unit test."
He gives a specific incident. His team allowed unreviewed code generation starting in July 2025, and production broke within four months. A misrouted primary key spread through the codebase, took days to find, and cost three weeks to re-onboard people onto code they had never read.
He expanded the same argument in a July 2026 AI Engineer World's Fair keynote titled "Why Software Factories Fail," which runs 19:18 on his AI Engineer speaker page. The thesis is that harness engineering (prompts, tool loops and orchestrators stacked on a model) cannot by itself produce a maintainable codebase at scale.
How much faster does AI coding make you?
The clip leaves out the numbers the full episode is built around. The episode description says you cannot get 10x with AI coding and puts the realistic ceiling at 2-3x, as long as you refuse to ship slop. The episode page quotes Horthy: "You can get 99% of human-quality code, like very good code as if you had written every character by hand, but two to three times faster."
The Pragmatic Engineer interview splits that into two cases:
- Roughly 30-50% lift when a human reviews all AI-generated code.
- 2-3x when the human spends the saved time on design, architecture and key decisions instead of reading every diff.
The same interview gives context-window guidance. Target 300-400K tokens of a 1M window, and stop around 100K on smaller models. Past that point he says the model degrades into what he calls the "dumb zone."
What Horthy recommends instead
On Dev Interrupted he describes RPI, short for Research, Plan, Implement. It is built for brownfield codebases. The agent has to produce intermediate design artifacts and settle architectural decisions before it writes code, so the decisions a unit test cannot check get made and reviewed up front.
Bottom line
The quote is accurate and comes from a long interview. The two smells he names have standard definitions, and both slip past tests and specs, which is why a model can follow a doc perfectly and still produce them. The full episode and the Pragmatic Engineer interview hold the parts the clip cuts: the 2-3x ceiling, the 30-50% review regime, and RPI as his fix.
Sources
- Original TikTok from @wordman.dev - the clip crediting Dex Horthy.
- Dex Horthy - What Actually Gets You 2-3x With AI Coding - episode 21 of The Weekly Dev's Brew, with transcript.
- The Weekly Dev's Brew - the show hosted by Jan-Niklas Wortmann.
- Full episode on YouTube - the video version of the episode.
- Context engineering with Dex Horthy, The Pragmatic Engineer - SWE-bench argument, the July 2025 incident, speed figures and context thresholds.
- 12-Factor Agents on GitHub - Horthy's framework, including Factor 3.
- Dex Horthy speaker page, AI Engineer - his background and the "Why Software Factories Fail" talk.
- HumanLayer on Y Combinator - batch, founding year and founder.
- Dex Horthy on Dev Interrupted - the RPI method.
- Tramp Data, DevIQ - definition of the smell.
- Code Smells: Tramp Data, luzkan - origin of the term.
- The Law of Leaky Abstractions, Joel on Software - the 2002 essay.
- Mermaid - the diagramming tool Horthy mentions as "mermaid charts."
Published September 25, 2026. Based on a TikTok by @wordman.dev. Full video notes (markdown)