Gerhard Lazu

And we know a thing or two about Erlang, Jared, right?

Because the application...

Elixir, the Phoenix framework, runs on the same principle.

I know a thing and you know two.

So that's how we get to a thing or two.

And Adam, I'm sure he knows the big one, but we don't know whether he's going to share it.

The point is, the point is, when you think about let it crash, Jared, in your, like from your development experience with Erlang, with Elixir, Phoenix, is there any situation, any moment where you could experience it and you realized, huh, that's nice?

When you let it crash.

Yeah.

So, you know, when you write code, we tend to write code very defensively, typically try catch.

So you feel like you need to account for every single scenario.

And the let it crash philosophy is about not preventing failure.

learning from it what that means is you need to have a context where it's safe for things to crash and the overall system will still remain stable so how can you build a resilient system really this is about resiliency where the core of the system will remain running and the system as a whole will remain running even though parts of it may experience failures but those failures will not bring everything down and that's really important so

fewer try catch blocks don't code defensively let it crash and separate the code that solves the problem from the code that fixes the failures and the more you can lean into the framework or the vm or whatever you have the system to deal with failures the better off you are to focus on the things that are unique to your application yeah and erlang is well renowned for that

Agreed.

Well, in our case, we had a lot of crashes to deal with.

So what we are going to have a look at is all the times that the pipe dream has been crashing.

since our last Kaizen.

So since Kaizen 2021, which is October 17th, we had a lot of crashes.

And there's a certain property about the system, and this is Varnish specifically, that made these crashes pretty okay.