Shyam Sankar1:20:56
Well, I think we should, you know, one of the mistakes we made was thinking like, hey, this thing is so expensive, we should plan to use it for 80 years. I mean, man, I don't even know what the world is going to look like in 10 years, let alone 80 years. Like, how do we get into tighter cycles of iteration? Iterate faster. In World War II, we had roughly 150 different airframes. You know, we think about like the P-51, the B-52, like we have these archetypal planes that we think of, but many of them we've forgotten. So, maybe we could say like 10 of those airframes really mattered, but we produced 150 different ones. And maybe that's roughly what that's the sort of chaotic innovation you need to you can't get to those 10 just by thinking your way through it. You need to kind of experiment and play your way through it. And most of them had a short shelf life, you know, and we got to be thinking about what is the true cost of doing this because sometimes I think we lull ourselves into a sense of if we just plan this out better, it'll be cheaper over the long run. And in fact, what we see is it's not actually cheaper over the long run. It becomes very expensive and you don't have any of the competitive pressure and it's not just internal competitive pressure it's the outside where the enemy gets a vote as we say so as they're changing we're going to realize that we need different weapon systems that are changing one of the lessons that I really highlight in the book is it's not actually what your weapon system does today that's determinative of victory it's how quickly you can change your weapon system to what you need it to do tomorrow this is why like the work with Detachment 2011 like the organic ability for green suitors to reprogram their weapon systems to do new and innovative things in combat is truly the advantage. It's kind of like the meta advantage. It's not literally just what does it do today, but how malleable is this weapon system to what I'm going to need it to be able to do tomorrow. How much of that can I do as I'm fighting? We see the Ukrainians do quite a bit of that, right? And certainly a large scale con it's not a one-to-one mapping between what's happening in Ukraine and what's going to happen, but there are absolutely lessons to learn. One of those meta lessons, another one is before the war, many of these infantrymen in Ukraine, I think the average age is 41 for a Ukrainian infantryman. Many of them actually worked in IT outsourcing firms. They actually have technical skills. Now, the infantryman is not writing code, but because they understand the technology, they're able to ask very precise feature requests like, 'Hey, I need it to do this.' and they know whether their request is going to take one hour, one day, one week, one month, and they titrate their request relative to like, yeah, if I get in a month, I might be dead. I'll settle for this capability in a day that I can use to apply effects on the adversary. So, it makes them better customers. And that alone, like, we need folks in combat arms who are principally experts in their combat arms, but also have enough technical literacy to view software as a weapon system that they know how to wield and fight off of that.