Dylan Ratcliffe

And so I could build a cool thing.

And because of that, it meant that I didn't actually need to make all that many trade-offs.

For example, it's always been a supported feature from day one that we can discover dependencies both within a single account in the cloud.

and across accounts and across different clouds and between on-prem and cloud instances, despite the fact that all of the things that do the gathering of that need to be installed in different locations.

They need to be highly available.

They need to have different authentication.

All of that has always been a feature.

Like the first demo I did had the ability to do all of that, which is massive overkill and totally unnecessary, but I didn't have too much time pressure and I wanted it to be that way.

and I had just come from working with like massive banks and things like that so I knew that at some point we were going to need those features so I didn't actually make that many trade-offs I basically built it the way I wanted it to be built and amazingly very few of those things have come back to bite me the fact like those features especially the fact that we support high availability out of the box the fact that we can bridge different clouds and stuff like that are now becoming extremely useful as our customers get bigger and more complicated

And it's the same code that I wrote right at the very beginning.

Nowadays, we have to make way more trade-offs.

I have customers and investors and a board and we need to be moving way more quickly than we did when it was just me sitting in my room.

I can't afford to go and sit in my room for eight months and come up with something.

And so we are making a hell of a lot more trade-offs now in terms of

getting things shipped, getting feedback on them and being able to iterate than I did in the beginning.

But yeah, remarkably, I don't regret not making those trade-offs.

Yeah, so while I didn't make too many trade-offs in terms of the architecture and engineering, we've made loads from the product side of things.

When we started, we were wrong about what would be helpful.

And we realized that pretty quickly.

So the first iteration of the product could discover all of the dependencies within your cloud infrastructure and show them to you.