Dylan Ratcliffe

And so that is what is next for the team is going as broad as possible so that we can support all of the different ways that people make changes to infrastructure.

It's one of our core values that users don't have to change their workflow in order to use our product.

Which means we need to take on the work of supporting every possible way that they could do it.

And now that the customers are getting bigger and bigger, that is becoming more and more important and it's more and more.

There's more and more different ways of people doing things, doing authentication, doing workflow, all that sort of stuff.

And the team's growing up as well in terms of the team is expanding.

We need to be supporting people around the clock.

We need SOC 2 and ISO 27001 certification, which means you can't just push to main with nobody reviewing it.

So not that we did that very often, even from the beginning, but we've had to grow up and we're going to have to continue to.

I think the person who most influenced me was my first manager at Puppet.

When I first joined, I was an associate, which was like the lowest.

In fact, they had to create a new level of professional services engineer because they didn't have one junior enough for me.

And he was an ex-Navy submariner and he was serious and angry and professional and disciplined and caring.

And I think he probably agree with most of those assessments.

But he would literally put his career on the line because someone working in a bank in Singapore couldn't do something they needed to do because of a bug in our software.

He would absolutely go to bat with engineering, with product, and he would make, he would be a pain in the ass.

I'm sure he was the absolute bane of their existence, and I'm certain they would have considered firing him multiple times because of how much of an incredible pain in the ass he was.

And he would get stuff fixed.

He would get things moved up the priority ladder because, hey, it's affecting this one sysadmin, and it'd get fixed, and then the next week he'd do it again.

There'd be some other sysadmin with no real influence sitting in not a very nice office in an industrial estate somewhere working on infrastructure who is blocked because of a bug, and the next week he would go out and put his entire career on the line again, getting on calls with product and