Noah Labhart

That means lower data volume, lower cost, and faster root cause analysis across your existing observability tools.

To see how it works, get a demo at mezmo.com slash codestory.

That's M-E-Z-M-O dot com slash codestory.

It's not just about technology.

All this and more on Codestory.

I'm your host, Noah Labhart.

And today, how Dylan Radcliffe is simulating incidents so you don't have to.

And you can focus on deploying your infrastructure today.

Dylan Ratcliffe lives in San Francisco for less than a year, but grew up on a farm in the bush in Australia, riding motorbikes and playing video games.

He fondly remembers the days whenever you could get a free version of Age of Empires from a cereal box.

He was always into computers and earned a scholarship to head into Melbourne for university.

He left his first job as an auditor with KPMG to join a startup called Puppet.

But outside of tech, he still rides motorbikes and has a super small one now.

It's actually meant for kids.

He loves all food, but prefers Asian and Indian cuisine.

Dylan was deploying Puppet at a financial services company and was pushing to get a win.

When a late Friday afternoon deployment went haywire, he decided to leave his company and set out to build something to automatically discover dependencies on a network to prevent deployment outages.

This is the creation story of Overmind.

Let's dive into what you would consider the MVP for Overmind.

How long did it take you to build and what sort of tools were you using to bring it to life?