LT Lauren Tan On Y Combinator Startup Podcast

“It took us quite a while to get to that point. It involves making sure your code base has good guardrails and constraints, so that the time you'd otherwise spend on human code review is encoded into your code base and your static analysis and tooling. When you have that much trust in your agent's ability to write good code, I've gotten to a point where I essentially have my agents merge their own pull requests.”

Y Combinator Startup Podcast · Startups & Venture · November 2026

“It took us quite a while to get to that point. It involves making sure your code base has good guardrails and constraints, so that the time you'd otherwise spend on human code review is encoded into your code base and your static analysis and tooling. When you have that much trust in your agent's ability to write good code, I've gotten to a point where I essentially have my agents merge their own pull requests.” — Lauren Tan, Y Combinator Startup Podcast

Context

She had just described building a whole feature in one Slack thread without opening her editor, and a host said very few engineers work this way. She explains what has to be in place before you stop reading the PR.

Transcript

Y Combinator Startup Podcast Around 30:03 into the episode
Speaker 4

And so the whole feature was built end-to-end in that one Slack thread with you and Samantha and Potato building it.

Speaker 3

…the gold standard for how to do it. And then I would say maybe like five or 10% of engineers or maybe 1% of engineers in the world are doing this right now. So this is literally something that should grow by a hundred axes. I'm unbelievable that like so few people are doing feature work this way.

Lauren Tan

Yeah, I'll say that, you know, it took us actually quite a while to get to that point. I feel like it's actually quite hard to get to that point overnight. It involves investment into making sure you have the right skills, your code base has good guardrails and constraints so that the time that you would otherwise have to spend on human code review is encoded into your code base and your static analysis and your tooling so that the engineer's time, yeah, like PSAC. And so your engineer's time is freed up to actually focus on the actual product, the user experience and the operational execution part of the job. When you have so much more trust in your agent's ability to write good code because you've set up those systems, I've gotten to a point where I essentially have my agents merge their own pull requests. So in that Slack thread example, that was an example of me not reading the PR. And we just looked at the artifacts that came out of it. So

Speaker 3

this cursor environment, does it already have PSTAC? And is that the way it sort of creates, you know, decides how to build it?

Lauren Tan

Yeah. So for internal, PSAC is installed into our repo. There's an internal version of PSAC. Instead of calling it potato mode, it's Lauren mode. And it just started because I wanted a place to put my skills. And so yeah, everyone in the company can actually use PSAC. And my cloud agents that the…

Speaker 4

We haven't really explained what PSTA is. Can you explain what PSTAC is for people who don't know?

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from Y Combinator Startup Podcast