“Before, you would say there's very low odds that you will lose hardware this year if you have enough redundancy, and low odds that you're going to be attacked if you raise the bar. But this has all changed drastically now. It's no more 'I have low odds that it's going to happen.' It's just: it's going to happen. So your only way out is to be sure that you can recover when it happens.”

…that was not even the discussion before. And of course, war, which is an active topic for us, since we've been contacted by people that had data in data centers that were struck by missiles. So not the kind of stuff I would hear about a few decades ago. Not that funny, but interesting. Interesting.

…have it backed up because it was a POC or I never properly operationalized it or anything. And that's all. That is an entirely other topic we can probably talk about on the show, which is how do you get your AI teams to enable teams to think about productionizing apps? But it happens a lot, right?

So I think we've done a pretty good job of talking about why everything is terrible and everyone should be scared as hell and everything. We're not always here just to tell you that you should just go retire off to a kettle and raise chickens in Montana or something like that. So let's think about…

So, I think there's two ways to reason about backups. More than backups, it's data resilience in a sense. The first one is that people usually do not categorize their data sets. So, it's more of a, yeah, I have machines, I will back them up, and they're all backed up with the same kind of level.…

That's what I was just going to say. It seems like, you know, and I'm a big believer in infra-code policy code. I mean, hell, the app that I use for tracking my workshops is work, or not workshops. My workouts for my lifting is a thing called Liftasor. And it's like workouts is code, right? You…