Harness Engineering is not Enough: Why Software Factories Fail

[upbeat music]

What's up, everybody? How we doing? [audience cheering] Guys, give it up for all the great speakers today so far. [audience applauding]

Um, all right. This is, uh, Harness Engineering is Not Enough and Why Software Factories Fail. And we're gonna click maybe. Ooh.

Oh, that's way too many slides. Hold on, guys. Okay. Um, so we're all racing to put AI coding into production, and, uh, there's been lots been said about loop engineering, and, uh, we should probably write more loops, and, uh, yeah, I don't know, I guess we're doing loops now. [laughing]

Uh, StrongDM built a lights-off software factory where nobody even reads the code, and the prevailing narrative is we should just spend more tokens. You are the bottleneck. The models are good enough.

Code is free. Just ship more stuff. But at the same time, we are starting to see the cracks. Our friend, uh, Mario at AI Engineer Europe begged us to slow down because companies that should not be having outages because of coding agents are having outages due to coding agent mishaps.

Um, codebases are falling apart faster than they ever have before. And our friends at Faros AI actually even did a report since we all picked up all these AI coding tools in January, maybe February.

Um, pull request, code review quality is way down. We're having more comments, longer comments, and tons of PRs being merged without any review at all. Incidents are way up, bugs per developer are way up, and, uh, many people will tell you that you're holding it wrong.

That's the only reason. You're not. Well, maybe you are- [laughing] ... but that's not the point. Um, I've spoken a lot about how to hold it better when it comes to working with AI.

Uh, probably a million views on YouTube at this point across a bunch of different talks. Um, and the basic thing is, like, as engineers, we've been told that if token maxing isn't working, then it's a skill issue.

You just need to spend more tokens. Uh, let go of reading the code. That with enough harness engineering, if we maybe sprinkle some magic words, adversarial review, on enough of our, uh, PR bots, that we can get the best of both worlds.

Ten to a hundred x faster, high quality, and nobody has to do that thing we all hate called code review. Uh, I'm here to convince you today that this is in fact not a skill issue, that no amount of harness engineering or loops maxing can solve what is fundamentally a model training issue.

That's why we say the harness is not enough. Um, and to understand this, we kind of have to grapple and dig into how coding models are trained. I'm gonna talk about what I think the shortcomings are with some of the current benchmarks and what better ones might look like, and we'll talk about how to move faster safely

in the meantime. Um, it's gonna sound like a rant, uh, but there is hope here. Uh, I'm gonna talk about our journey and a bunch of the landmines we've hit, uh, building in this world, a bunch of exciting new techniques that we've been working with, uh, a lot of our users and customers to de- develop, and I

think how we all as a community get to the next chapter of agentic engineering after whatever this thing that we're in. Um, so we use a lot of words here.

I'm gonna zoom out a little bit. I wanna give you kind of like a brief history of the software factory. Um, and there's actually... I don't-- I, I, I just learned this last week.

Uh, it was-- the term software factory was defined at a NATO conference in nineteen sixty-eight. Uh, we're gonna start around twenty twenty-two, like right before AI started coming around.

Um, and basically in a typical twenty twenty-two software factory, you will have some people building stuff. You'll have engineers, you'll have PMs, maybe you have some sort of leadership team that is driving the vision here, and they all decide that stuff needs to get done.

And so you put it in a Tracker, a Linear, a Jira, a Beads, some sort of state machine that tracks what needs to be done, and then someone goes and grabs something off of there, and they build the thing.

And there may be some automated testing in that process, maybe some ma- manual testing in that process. At a certain point, we make this pull request thing. Says, "Okay, cool, we gotta run a bunch of checks, automated stuff.

A human's gonna review the change and review the code, and perhaps we might even have, uh, a human pull it down and test it somehow." And if anything goes wrong here, we loop back to someone builds the thing, uh, and eventually we're ready for prod.

And so we ship it to production, and once it's in prod, it makes contact with our users. And users do, uh, a thing that, uh, we all love. Uh, users love to complain.

I, I love our users. Uh, but yeah, they're gonna ask for things, they're gonna find bugs, they're gonna file feature requests, uh, and that goes back to your team.

You might also add monitoring. And so, uh, you know, what do we want more than anything else? We wanna wake up engineers at three in the morning when something breaks, so they can get dragged out of bed to try to go fix it.

Uh, and we go on and on in this loop, uh, and we ship a bunch of code. Um, and one thing that we noticed here is that, uh, teams figured this out decades ago, is that this someone builds the thing step is usually going to take hours or days in most cases.

And the review part will also take hours or days for large things. And so teams started doing these upfront planning, architecture proposals, sprint planning, and they would collaborate this o- on, on these things as a team, uh, with the hopes that we might decrease the percent chance that something would need to be reworked, that we would be

able to re- reduce the time spent in reviewing every line of code because we aligned on everything ahead of time. This brings us to the agentic software factory. Uh, every company and their mother is talking about how they built a coding agent factory that ships seventy-five percent of their code now.

Uh, literally everybody.

Uh, and so if we look at the software factory from 2022, uh, we just replace someone builds the thing with an agent builds the thing, and we have an orchestration and a harness and a sandbox and a model and computer use, and I'm not gonna get into, like, the details of that.

You can watch 100 talks about that this week, I'm sure. Um, but now the building part takes minutes or hours, but this human part still takes hours or days if you're gonna review the code and you're gonna test the changes.

And so we bring in agentic code review, and we bring in agentic regression testing, uh, and it makes this part faster, but it's probably still the bottleneck. But we can do more loops here.

Why not? Let's do some more loops. So we can route all incidents straight into the factory. Why does someone need to get woken up, uh, and try to fix it when they could just wake up to a pull request and, uh, maybe that fixes the issue for you?

You can take all the user feedback and just stick it straight into the factory so that, uh, people ask for stuff and it gets built. And now your only job is how much things can you stuff into the queue of stuff to do, and how fast can you review and test the changes?

Which brings us, of course, to I'm sure you know, the lights-off software factory, where basically Dan Shapiro coined this, is we no longer read the code. We say, "You know what?

This is going great. That code review thing, no thanks. We're just not gonna do that anymore." Uh, and we invest into all these other parts of the system, your, your testing, your monitoring, your rollout, everything else.

We just write more code and build those systems better, and now our job really is just how m- how much stuff can we ask the agent to build?

I am going to posit that this does not work, uh, and this is why software factories fail. Um, as, as an aside, what I'm going to say has nothing to do with vibe coding.

So Addy had this, uh, great post. I'm gonna just go literally take his quote verbatim, "A developer vibe coding a side project a dozen people will ever run, and a team keeping a 10-year-old enterprise system alive for another quarter share almost no constraints worth naming.

And most of what you hear on the internet is one of these groups of people telling the other group of people how to live their lives."

So if you love vibe coding, please go on. Um, at HumanLayer, what we care about is how do we help people solve hard problems in complex codebases? Um, we use the word brownfield a lot, which historically has meant, like, some 10-year-old Java thing.

I actually think agents really start to struggle after maybe three to six months, especially with the pace at which we can ship now. Um, you can ask me how I know this, and I will tell you that it is because in July 2025, we tried this.

We went full lights off and, uh, if you have tried this seriously for a number of months, you probably found at least one issue that the agent couldn't solve.

Even with your most advanced prompting, you do research, you do reproductions, you just-- you have to go and dig into that codebase that you stopped reading three months ago to try to figure out what's broken.

And in the meantime, your site was down, your users were pissed, and you were-- if you were like me, you were probably miserable reading all this slop code that you let s- s- slip into your system.

And what I wanna get to is basically models have a shortcoming. Um, they can't maintain and improve codebase quality over time, not without a, a decent amount of human steering.

Um, and when I say maintainability, I'm basically talking about issues like it becomes really, really hard to make a change in one part of the codebase without breaking other parts of the codebase.

This is Martin Fowler's shotgun surgery textbook code smell. Um, I'm not gonna say much more about maintainability. There's a bunch of books that you can go read about it.

In fact, John Ousterhout is actually here speaking this week, so you can go ask him in person about the philosophy of software design if you want to. Um, but it brings us to this question of, like, why can't models do software maintainability?

Um, and you may also be saying, "But Dex, you know, surely the models have gotten much better since then." Um, they've gotten better in some ways, but they're still about the same in others.

Um, if you wanna solve one-off problems or vibe code a new mar- marketing site, yes, they got way better since 2025 and 2024. But as far as improving codebase quality, I think, uh, they have not gotten much better.

Now, I cannot prove this because there are no good benchmarks for a model's ability to maintain codebase quality, and I'll get into, like, where we're going with that. Um, but if you've worked with coding agents for a while, a lot of people are posting about this, it's just like you probably have this vibe that they, they generally

make things worse over time and make the codebase harder to work in. And to figure out why this happens, I wanna zoom out to the first great coding agent.

Why did Claude Code go from nothing to four billion, and I think now they're at nine billion in revenue in under a year? 'Cause there were great CLI agents before Claude Code.

You had Aider, you had Codebuff. There was a bunch of tools in this category. They had all the same tools, read, write, edit, grep, bash. Um, so what was the difference?

The difference was, was that the-- this was the first time that a model lab trained a model against the harness that they were gonna distribute it to users in.

Um, and it got really, really good at-- this is just some of the tools, but it got really, really good at calling these sorts of tools in an agentic loop.

In fact, the OpenAI team did a talk in November about basically if you are a, uh, harness builder and you don't own the model weights and you can't RL the model in your harness, you will always be at a disadvantage compared to somebody who owns both the model and the harness.

Um, and I'm gonna cite a couple slides from my buddy Calvin French-Owen, who was a MTS on Codex during the initial launch. Um, but LLMs are just next-token predictors.

Uh, this is a slide from over a year ago where basically as you're doing your agentic loop, context window goes in, next step comes out. And, uh, we're gonna try to do this.

I haven't actually timed this, but we're gonna see if we can do coding agent reinforcement learning in 60 seconds. So what we're gonna do if we wanna train a model to get better at tool calling, better at solving software problems, we're gonna generate a bunch of-- we're gonna give it a problem, and we're gonna generate a bunch

of traces. Try to solve the problem a bunch of different times. We're gonna score them all on correctness and did the test pass and all this stuff. Uh, and then we're gonna reinforce.

We're gonna make the bad behavior less likely, and we're gonna update the weights to make the good behavior more likely. Um, this, one of the classic ones here is SWE-bench Multilingual.

Uh, they're about 15-minute tasks. They're from open source repos like Redis, jq, and Django and all this stuff, and they have binary one or zero rewards on did you fix the problem you were trying to fix, and did you do it without breaking anything else?

Um, and we look at actually a real problem from one of these benchmarks. This is fastlane, which is a Ruby project. Um, basically there was some issue where we weren't checking for nil, and we have a stack trace blow up because you have a null pointer exception.

And in this, um, in this benchmark, you have a base commit that we're gonna check out before the issue was solved by a human in the past. We're gonna give it a test patch that says, "Here's what the behavior should be afterwards."

We have a golden patch. Both these are hidden from the model. Uh, and so we have the agent go try to solve the problem. We store its patch. We undo all the changes it made to any test files, 'cause I'm sure you've seen models comment out tests just to get things working.

And then, um, we're going to apply our golden test patch, uh, and then we're gonna run the test. Old test and did the new test pass, and if they both pass, then, uh, then we get the reward.

Otherwise we don't. Um, and so models are trained to get the test to pass. There's no way in this system that we can penalize it for poor program design or for eroding the maintainability of our systems.

That's why we get things like this, try-catches around things that probably don't need a try-catch, or things like this. I think Vaibhav gave us this example earlier of casting things to other things just so the model can just, just, it just wants to get the test to pass.

Um, and so if you can't verify the, uh, maintainability of the code, it gets way harder to train on this stuff. Um, so you remember this picture. Verifying code quality and maintainability is orders of magnitude harder than the code runs and the test pass because the cost function of bad architecture is measured in months and years.

If you have a coding episode and then you only find out months later that like, oof, somebody vibed this a little bit too hard, it's really hard to propagate that reward signal back across the gap.

And now the frontier is getting better slowly, and since I know someone's gonna be in the YouTube comments about this, yes, I know benchmarks and verifiers are different and they actually have to be separate data sets, but they're shaped the same and the, the structure of these benchmarks is directionally correct, so we're gonna look at these as

like, what is the future of evaluating code maintainability? Um, there's a really cool one called SWE-Marathon from Abundant AI where they do like four hundred hour tasks of like clone all of Microsoft Excel, every single feature.

Uh, and they have some sophisticated reward channel stuff. Uh, DeepSWE from Datacurve is also like large tasks on OSS repos that are not actually in the training set 'cause they were never actually built in the real world.

Uh, and then you have Frontier Code from Cognition, um, which is multi-PR tasks. They do interesting things like, hey, if the model writes tests that don't fail on the pre-patch code, then it gets penalized.

And then we have a judge model that says, "Okay, uh, did this follow all of our code quality rules?" Um, so we're getting better, but I think models judging quality can only go so far.

Uh, 'cause if the new model-- if the model knew what good code looks like, it would probably write it in the first place. Uh, and review agents and throwing more tokens at the problem, it can raise the floor, um, but we're still constrained by what we can teach during RL.

Um, and so I will, I will posit that for now we're stuck reading the code, uh, but we can still move pretty fast. And of course, there's a world where this is solved, uh, in the future, and if you wanna just keep YOLOing prompts until you get to GPT-7 and you don't have to think about this, by

all means, please. Uh, but bitter lesson be damned, we've got some problems to solve, so let's engineer our way out of this. Um, so turning the lights back on, we're gonna put the code review back.

Uh, we're gonna embrace this approach of like how do we plan up front to reduce the chance that we have a long or a difficult review process. We're gonna find leverage.

We're gonna use AI to help with this. Um, the first thing we're gonna do is we're gonna do some sort of product review, understanding what problem we're solving, what's the desired behavior, maybe looking at mock-ups.

Here's a product review I was working on yesterday with a mock-up of a new feature. Um, once we have our product review, we're gonna... And by the way, we don't-- small stuff still just goes straight to the agent.

Um, but once we have the product review, we're gonna also do architecture, system architecture. A lot of people have been doing this for a while, component contracts, data models, constraints.

Um, this is an example of a doc that we build to understand how these systems are gonna fit together and what's like the high-level picture of it. From there, we do something, uh, that I think is really under-emphasized in, uh, agentic coding these days, which is program design.

I think people assume that once you get the architecture right, the model can just cook. Um, but we're all-- I-- we often look into the types and the method signatures, the program layout, and the call stacks.

And so here are some examples. I don't think you'll be able to read this one, but this is like the level of abstraction we're at, is how are we actually gonna lay this stuff out and how are these systems gonna interact?

Uh, Dylan Mulroy from Cloudflare talks a lot about how he's using these call graphs as part of his planning process. I think this is exactly right. Um, and then once we've done the proto- program design, we can do this thing called vertical slices, um, which is the order of implementation, multi-repo coordination, how are we gonna build this

across our entire system, and how are we gonna check it along the way? I've talked a little bit about how models have horizontal plans. I won't go too deep into it.

If you want to learn more about this, you can go watch our talk from AI Engineer Miami. Um, couple shots of a doc like this going through the tests and the steps in between each phase.

Um, the main idea here is thirty minutes over here in pre-planning and alignment can save you hours in review. And so it's actually feasible to still read every line of code.

Um, we'll skip this part. Uh, basically the, the summary here is like you don't have too many PRs. If you're drowning in PRs, you actually have too many bad PRs, um, because a good PR is a joy to, to review.

It's, it's-- you're just reading through it like, "Yep, this is great. This is what we discussed. This is what we talked about." Um, but even if a PR needs twenty percent rework, which is generous for a lot of AI, AI vibe coded slop, um, it's an em- it's an emotional and intellectual burden on both the reviewer and

the submitter. Um, and so if you use model-assisted planning and alignment, your alignment is shorter 'cause you used AI to get all the information at once, your code review is faster because you aligned up front, and your coding is faster 'cause AI did it.

And so you're now you're actually really moving faster, but you're still reading everything and you're still owning the code. So closing advice, um, it's easy to hear all this and be a little bummed out.

Uh, I really like the world where we just YOLO everything and we can just like not have to ever read code ever again. But, uh, we're engineers, and these are just constraints, and models are good at certain things, and they're not good at other things.

And so go figure out how to solve problems given a set of constraints. Uh, use loops. They're great. Go solve hard problems. Seek leverage. Um, if you want help with this, um, we're building HumanLayer.

HumanLayer is an AI IDE and collaboration platform. It's building blocks for your software factory, um, and soon to be better vi-verifiers for software quality. Um, we've got sort of a Figma for Claude Code and Codex style collaborative workspace.

It walks you through the workflows for doing this sort of work. And, uh, we are talking to design partners. We are hiring founding engineers here in San Francisco. And, uh, these slides are live.

You can go get them right now. You can try HumanLayer at humanlayer.com. Uh, it's free for small teams. Go solve hard problems and complex codebases. Thank you all for your energy. [audience applauding] [upbeat music]