Dan Shipper

So that when we launch it, if there are problems, it's not just me in my foxhole trying to understand the code base while it's going down and everyone's looking at me.

Because that's pretty stressful.

You can switch off.

You can switch every other night.

Exactly.

And that...

led me to this articulation of how early product engineering teams should work which is the pirate and the architect model where okay you want a pirate and that's i'm a pirate which is like you're just going you're just going as fast as you can you're just trying to find something that like works and people like um and then the architect is a little bit like i want to really understand how the whole system works and make the whole system work together well as a well-oiled machine

And especially in early product work, you actually don't need a full time architect.

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.