Dylan Ratcliffe

This is what we need to be doing, and this is what we need to be getting better and better at.

We're now at the point where we can simulate up to 10 layers deep.

with an unlimited number of dependencies in between those 10 layers, which is awesome, but that is going to keep changing.

This is the sixth complete rewrite of that process, and there will be a seventh, and I already know what some of those features are going to be, so...

Working on the core of the product is always just a never-ending thing.

It is never done because it needs to be vastly better than a human.

And so it's never-ending.

But the other thing that we need to do now is that we've gone from having a few smaller customers to...

working with some very large regulated businesses we're now a mandatory step in the production process the go to production process for regulated financial institutions like we're assessing the impact on stuff that processes millions of dollars a minute in terms of transaction volume things are starting to get more serious and that's one of the things that dictates the future of what the product looks like and what the team looks like because these companies are

getting bigger and bigger.

It's not really my choice.

It's more the market is telling me that I need to be going after these bigger companies because they just feel this problem most acutely.

It means though that we need to expand our feature set of what we support.

We started just with AWS.

We recently launched GCP.

We're working on Azure at the moment.

We

currently support Terraform but we also are building Pulumi and Argo CD and even supporting manual changes the bigger the companies get the more guaranteed it is that they will use every single tool in existence and so if you need to go after those bigger companies if you want to be able to be

mandatory in the sort of massive heterogeneous workflows that they have.

You need to support every possible way of doing an infrastructure deployment.