Paul Dix

So the problem is if every engineer can do that in a brief amount of time, then again, you have this problem of, OK, it's too easy to produce this stuff.

And who's going to review it?

And who's going to like?

I always feel like the 37 Signals model of like, OK, whenever we do a feature, we put two people on it.

I think that's almost like the way to go.

It's like you have two humans on something.

They don't necessarily need to pair program or whatever.

But then you actually limit the scope of, OK,

You have somebody who can review your stuff closely.

And again, like we don't, our engineering team doesn't have that.

The thing is we have a bunch of different engineering teams with different responsibilities, right?

Some of them are,

There's an engineering team that supports V1 of the product, the hosted version and the on-prem version.

There's an engineering team that supports V2.

There's an engineering team that supports the iteration of V3 that we currently have hosted.

There's an engineering team building this new version of V3 that we have as an on-prem product and also hosted in AWS.

It's a time stream for InfluxDB.

It's actually like an AWS first-party product.

So every team is like kind of a little bit different in terms of what the scope of their responsibilities are and what they care about.

I think, I think Bezos had potentially a larger team in mind, like up to like eight or 10.