O11ycast · Hands-On Engineering Podcasts · November 2026
Obie is explaining his "regenerative software" approach: exhaustive contract tests plus a record of every decision behind the requirements, from which agents can rebuild the whole implementation.
Like just how big the swings can be, how ridiculous the concept can be, how big the lift. Pick your metaphor, whatever works for you.
Like what we can do now?
Yeah, what you can do now, which sounds super like cliche or like, you know, yeah, everyone's talking about that. But I'm like, like today, today I was talking to someone and I was like, you know, I just realized I'm completely reinventing the way software is made. They're like, what do you mean? Yeah. It's like, well, yeah, it's like we're all, don't hate me for this, you know, but like we're trying to figure out these kind of ways to use AI. But I'm like, hey, if we go back to first principles, and this is heavily influenced by Chad Fowler, so I don't want to pretend like I invented regenerative software, but I have been, apparently, from what he tells me, doing a lot more hands-on stuff with it than, you know, anyone that he may be talking to. I don't know for sure. I got to ask him that. But anyway, I'm doing a lot of stuff with regenerative software and I've been talking about it. Right. And one of the things that I'm doing that I guess in retrospect falls into the token maxing kind of world because it chews up a ridiculous amount of tokens is to do this contract first, exhaustive, automated testing around the requirements of the system and…
Four what?
So one orchestrator process running Opus 5.5 and it's driving four implementation lanes.
Oh, lanes, like LANAS.