Y Combinator Startup Podcast · Startups & Venture · November 2026
A host asked how much code review is enough, since his review step burns tens of millions of tokens. She answers that she has moved away from adversarial multi-model review and puts the effort into the code base and static analysis instead, so the agent gets it right the first time.
question. I think. So for me, actually, in PSTAC, I have tried to downplay some of the review skills a little bit. In PSAC, we have a bunch of skills. There's one called Interrogate, and that will spawn agents of different models. So across different families,
which works really well, you can do like adversarial review.
That was quite hot many months ago. I've actually kind of withdrawn a little bit from that because I've Find that when you do that, I mean, it's still valuable, but I think you run the risk of overfitting, where the sort of agent doesn't have the ability or maybe enough judgment to determine what's actually good feedback versus not good feedback. And it maybe doesn't have complete knowledge of your goals and your intents and your, you know, your wider product vision. It doesn't understand how you want the product to evolve, for example. And so you can get to a point where you are, you know, very abstractly, you know, it's kind of like imagine before agent, you have a bunch of engineers talking about the most perfect, ideal utopia way of doing this. But actually, you know, that doesn't even matter because in two months, we plan to deprecate this thing and build a completely new vision. And so I think there's some similar analogy there where I think some review is good, but I try to move more towards like on my screen here. I have this inverted pyramid…
You just gave me a feature idea, which is like, because GStack has office hours and like the CEO review where you're like talking about the product, I can use that. I mean, because those are like product requirements that feed in. Right. Yeah. And those save to markdown in the project. So I could…
Yeah, I think so I intentionally drew it this way. I guess it's not a very scientific chart, of course, but the way I imagined it when I drew it, I think this is in terms of where you should spend your time as an engineer. So for me, most of the investment I make is into the code base and then…
Is somehow enforced in static analysis? Actually, like can know how long something will take to run?