Welcome to another bonus episode of the Tech Mem Ride Home, another portfolio profile episode.

This is sort of a hybrid because we're going to talk to a company that Ride Home Fund is invested in,

but it's also going to be sort of a newsy explainer episode. We're going to talk a lot about that big crowd strike

outage because today we're going to talk to Dylan Ratcliffe of Overmind.

And this is what Overmind does is help people prevent things like this from happening.

So Dylan, thanks for coming on.

Thank you for having me, Brian. So let's just start there. Tell me what Overmind does, you you know sort of a you know 30,000 feet sense and then we'll drill into what happened with crowd strike.

I mean you're exactly right with saying that we're trying to prevent these sorts of

outages outages where you make a config change where you think it's a good idea and

it turns out to be a terrible idea hopefully not a terrible as a crowd strike one

but we calculate the blast radius work out the

dependencies and do a risk analysis in advance so that people can know that, you know,

pressing this button could potentially ground all the flights in America before they press the button.

I love that term blast radius but obviously you know there was a huge blast radius

with the over with the crowd strike thing but go into more detail about being able to

identify those risks ahead of time because that's the key here once you've hit the button it's it's too late as we've seen.

Yeah the only way that we can do that is by understanding the blast radius and the context to what we've found and it's the case in the

crowd strike out it is the case in every outage that I've studied where I've

been involved and when I've studied just from stuff that has been put out on the

web like in like in the crowd strike example is that the change that you were

making was not bad on its own. It was only bad when combined with other latent factors that

already existed within the environment.

...