Burke Holland

What happens instead is that you, you think you know, you discover it as you go.

That's right.

And it changes and you make trade-offs and the agent has to do the same thing.

And so I don't know what the answer to this is other than whatever product you and I are replacing is,

currently probably has a team of devs and an engineering lead and every monday morning they get together in a stand-up and maybe they have a stand-up every day where they go over all of the work that's in the backlog what the status is on each one of those things and i almost wonder if that isn't the future right because you can't just hand this work off and then just walk away and expect that the agent is just magically going to know

exactly what you want.

It just doesn't.

And so in order to really build anything of size, you'd almost have to have a daily standup with your agent where you go over all of the things that it's working on and review it.

And that's tedious.

That's actually the part no one likes, right?

Like Chad, if you're listening to this pod, like if you're in a daily standup, you're like, that's my least favorite part of the day.

I'm with you.

But there are reasons why we have processes and that's so that we can actually build things that work.

I did something similar where I have a Ralph loop.

I have Copilot CLI running in a loop.

And it's building a multiplayer game where you just LARP as a baby bird.

And you're hatched from an egg, and you fly around.

And I'm letting it.

It's deciding everything.

It decides what features it should add.