Dan Shipper

The first step is planning, where it takes into account all the best practices, all the stuff you've learned in building your product, all that kind of stuff.

It makes a really, really detailed plan.

Then you kick off your agents to work on it, and often you do that in parallel, so you have a bunch of agents all working in parallel.

then you review or assess what happens.

So you have tests and you maybe test it manually, you maybe have a fleet of agents do testing, and then you compound that learning.

So you take everything that you learned and push it back into the first step of the process and that's what makes it compounding.

I think

This is something we were on early.

This is something that Kieran in particular really noticed and was like, I'm doing this.

And I was like, that's sick.

And I think has become, even if it's not called compound engineering, has become a standard way that a lot of the model companies think about building engineering harnesses and doing programming.

So it's pretty cool.

Yeah, yeah, yeah.

Totally.

Um, and yeah, different people like using, even if it's not a specific skill, it's just like, remember this for next time you're effectively compounding.

It's the same kind of idea, just on a bigger scale.

Like definitely a lot of people, a lot of non-technical people in cowork, for example, use it all the time and love it.

And that's awesome.

There's something about the models right now, which I think will probably always be the case where if you just get them to think more or like use more tokens on your problem and do more research and spend more time on it, you just get better results.

And I think compound engineering, the plug in is a hack for that where