Dan Shipper

I think you just need you just need a pirate just like going hard and an architect coming in for a couple hours a week to be like, here's how all the things work.

And here's here's how we can tuck in the edges a little bit so that

The core of it is stable, but you don't really want someone spending all their time making it perfect if you don't know if it's any good and you want to be able to explore as fast as possible.

And sometimes some people on our team are kind of both.

They can kind of flip in and out of pirate and architect mode, and I'm just not that.

I just am not careful.

Some things I'm very careful about, this I'm not.

Um, and so you also have a lot going on.

Yeah.

So I think that's a good, I think that's a good model and I would expect to see more of that.

And, and we definitely see that across, you know, run five or six products internally.

And we definitely have, we have one person who's fully responsible for it all the time.

And then they often have one or two people who are spending some, some part of their day on it, helping them with, you know, some of the big, difficult, more architect tasks.

Yeah.

Um, there's a new way of building software.

I've been calling it, um, building software that's agent native and it implies a new architecture for how your software works.

Um, and the way that you can think about it is normally in software, um,

Any piece of software is like a recipe.

It has a set of steps for how it works, and those steps are known beforehand by the programmers.

In this new version of software, instead of the whole thing being written out beforehand, it's essentially cloud code in a trench coat.