WEBVTT 00:03.918 --> 00:09.001 [SPEAKER_00]: because I was deployed to Iraq, 2016, 2017 timeframe. 00:09.061 --> 00:12.803 [SPEAKER_00]: I was doing a light ISR mission with special forces. 00:13.043 --> 00:16.265 [SPEAKER_00]: And I was in charge of an Intel operation. 00:16.285 --> 00:24.089 [SPEAKER_00]: And we, there was just a tactic that we were doing that involved Excel in a very, like, Kalkiwak. 00:24.409 --> 00:24.910 [SPEAKER_00]: And, uh, 00:26.078 --> 00:32.903 [SPEAKER_00]: You know, it was very obvious, like, you know, when the hair starts standing up on your neck to be like, this is so inefficient, there must be a better way. 00:33.083 --> 00:33.263 [SPEAKER_01]: Yep. 00:33.383 --> 00:35.344 [SPEAKER_01]: And this is all quiet on the second front. 00:35.564 --> 00:39.867 [SPEAKER_01]: Podcasts were boring conversations around defense tech and national security come to die. 00:40.408 --> 00:49.874 [SPEAKER_01]: Join me, Tyler Sweat, and my second front homies, as we dismantle the mundane and cut through the bureaucratic bullshit to demystify the world of defense tech. 00:50.635 --> 00:55.238 [SPEAKER_01]: But be warned, this is not a typical government podcast, we're ready to get weird. 00:59.957 --> 01:00.697 [SPEAKER_01]: What's up, everybody? 01:00.857 --> 01:01.958 [SPEAKER_01]: I'm your host Tyler Sweck. 01:02.038 --> 01:04.698 [SPEAKER_01]: Welcome to another episode of All Quiet on the second front. 01:04.759 --> 01:07.039 [SPEAKER_01]: The podcast we're boring defense talk comes today. 01:08.320 --> 01:09.100 [SPEAKER_01]: Super excited. 01:09.140 --> 01:11.461 [SPEAKER_01]: Got an interesting story, really cool company. 01:11.561 --> 01:13.061 [SPEAKER_01]: Jay from Blets, you think it's come by, brother? 01:13.241 --> 01:14.001 [SPEAKER_00]: Yeah, thanks for having me. 01:14.121 --> 01:14.682 [SPEAKER_01]: Thank you, I'm in. 01:16.532 --> 01:21.856 [SPEAKER_01]: So we're a little rippin' about it a little bit offscreen, but maybe more of a non-standard background. 01:22.337 --> 01:30.303 [SPEAKER_01]: Hello, so much standard at the beginning and where you are now, but for everybody who doesn't know what's your story, how'd you get here and what are you working on now? 01:30.825 --> 01:36.290 [SPEAKER_00]: Yeah, so I started out at the Air Force Academy, like, you know, even to the West Point. 01:36.310 --> 01:37.431 [SPEAKER_00]: So I'm pretty standard there. 01:37.551 --> 01:39.352 [SPEAKER_00]: I was an Intel officer for about four years. 01:39.893 --> 01:45.878 [SPEAKER_00]: My last job was actually teaching economics back at the Academy, so I was a great train. 01:46.919 --> 01:48.280 [SPEAKER_00]: Thereafter, I separated. 01:48.340 --> 01:56.007 [SPEAKER_00]: I still stayed in the reserve, so I'm still serving the DIEU, which has been cool and also an experience to stay involved and stay in the community. 01:56.887 --> 02:00.450 [SPEAKER_00]: But thereafter, I did a JDMBA for four years. 02:01.711 --> 02:16.823 [SPEAKER_00]: I tried to do some entrepreneurial work in the midst of that, but ended up going into corporate law for about a year, right after grad school, and then I had great friends and connections from grad school that formed the company, let's see that I'm now working at. 02:17.984 --> 02:21.167 [SPEAKER_00]: They raised a growth round about eight weeks ago, 02:22.107 --> 02:27.372 [SPEAKER_00]: I timed my exit from Biglaw and jump in into Blitzie to set up their public sector function right at that time. 02:27.412 --> 02:39.042 [SPEAKER_00]: And so, you have the last eight weeks have been quite a surge and quite a fire hose getting back into the deck, you know, the tech world, and then, you know, we're obviously 02:39.729 --> 02:53.120 [SPEAKER_00]: As the public sector setting up more of like a defense and federal motion, so it's been it's been exciting and a bit non-standard in that in that sense, but it's great to kind of come back to the community that I see that a lot of time and for sure. 02:53.540 --> 02:56.563 [SPEAKER_01]: Yeah, so for folks, you don't know, give a little bit of run out of Blitzie. 02:57.243 --> 03:03.668 [SPEAKER_00]: Yeah, so Blitzie's the world's first autonomous software development platform built on infinite code context. 03:04.769 --> 03:07.912 [SPEAKER_00]: You know, we infinite code context, that's our term for how we 03:08.636 --> 03:12.620 [SPEAKER_00]: managed context and also orchestrate agents at massive scale. 03:13.100 --> 03:28.335 [SPEAKER_00]: So we've been built for the enterprise from day one, so attacking massive complex legacy code bases and the very critical use cases that those enterprises require. 03:28.835 --> 03:43.350 [SPEAKER_00]: And using the power of LLMs in a proprietary unique way to address those use cases at velocity and capability that we think is very unique and differentiated. 03:43.490 --> 03:44.811 [SPEAKER_00]: Yeah, I think it's super cool. 03:44.851 --> 03:45.091 [SPEAKER_00]: I think. 03:46.012 --> 03:53.955 [SPEAKER_01]: As you can see, you know, even the consumer side with the amount of change you are seeing from the diffusion of some of these capabilities in this technology. 03:54.035 --> 04:00.997 [SPEAKER_01]: It gets a lot of folks to go, you know, a lot faster, maybe do a lot more sort of like a hyper empowered individuals. 04:01.697 --> 04:12.043 [SPEAKER_01]: You know, taking maybe your last job and your new job, how do you see sort of that intersection on like trust and secure to because speed always isn't better. 04:12.504 --> 04:12.964 [SPEAKER_01]: That's right. 04:13.044 --> 04:15.265 [SPEAKER_01]: And we've got to get like that resilience that trust. 04:15.706 --> 04:16.446 [SPEAKER_01]: How do you see that? 04:16.486 --> 04:17.787 [SPEAKER_01]: How are you guys sort of thinking about that? 04:18.545 --> 04:19.565 [SPEAKER_00]: Yeah, no, it's a great point. 04:19.605 --> 04:33.830 [SPEAKER_00]: So I think we're a lot of the market is right now is with these IDE based, iterative-based coding tools that we say are incredible innovations in technology. 04:33.850 --> 04:40.372 [SPEAKER_00]: They can make software development, software developers, and the software development teams just incredibly more efficient. 04:40.432 --> 04:47.355 [SPEAKER_00]: However, I think something that we're seeing, if you look in the data, a very small percentage of that code that's actually generated 04:48.597 --> 05:07.145 [SPEAKER_00]: You know, roughly one L-O-L-M or one of these coding tools actually gets pushed to production and it's having, you know, the difficulty is being able to have the entire code to state in mind while writing that code such that, you know, the code you're writing doesn't break something, you know, in a very distant part of the code base and so. 05:07.705 --> 05:16.848 [SPEAKER_00]: The way we're attacking that issue is via, again, our proprietary way that we're engineering context, orchestrating agents around that context. 05:17.328 --> 05:25.410 [SPEAKER_00]: And then the biggest part is that, you know, it's not an SS, what sees platform isn't necessarily a turnkey solution, and that you just hit enter. 05:25.450 --> 05:27.470 [SPEAKER_00]: And then the agents go generate the code. 05:27.490 --> 05:30.771 [SPEAKER_00]: It's a very human and the lead gated process. 05:31.131 --> 05:33.012 [SPEAKER_00]: It's really the software development lifecycle. 05:33.712 --> 05:35.533 [SPEAKER_00]: Human field chat make no mistakes. 05:35.593 --> 05:36.133 [SPEAKER_01]: Yeah. 05:36.753 --> 05:37.914 [SPEAKER_00]: Yeah, exactly. 05:38.314 --> 05:50.161 [SPEAKER_00]: It's a very consultative process that we work with our clients, but the humans are making the decisions all along the way, and then at the very end, you know, are able to, again, make the decision as to whether or not to push that code to production. 05:50.221 --> 05:52.402 [SPEAKER_00]: And so I would say that's the main way. 05:52.442 --> 06:02.388 [SPEAKER_00]: We have other ways in which we orchestrate the agents to enhance security, you know, autonomous QA and testing and whatnot, which we could get into more. 06:02.548 --> 06:05.070 [SPEAKER_00]: I'm obviously not the most technical as we talked about, 06:05.990 --> 06:08.291 [SPEAKER_00]: Yeah, those are some of the ways where we're attacking it. 06:08.391 --> 06:16.494 [SPEAKER_01]: No, I think that human in the lead aspect, you know, removes maybe some of the concern, you know, anecdotally it folks say, hey, this is kind of like a black box. 06:16.554 --> 06:17.614 [SPEAKER_01]: I don't really understand. 06:17.654 --> 06:18.995 [SPEAKER_01]: Like I see what came out. 06:19.175 --> 06:22.136 [SPEAKER_01]: I sort of maybe see a prompt or, you know, a codebase that goes in. 06:22.916 --> 06:33.160 [SPEAKER_01]: But I don't tear point, like, understand the context of the rationale and then, you know, maybe that's a limb fact for the developer, but then on the recipient side for somebody taking a security view to it. 06:33.940 --> 06:43.209 [SPEAKER_01]: pretty difficult is you're trying to sort of like slash through, you know, not to say slapper anything, but just a high volume of contextless code. 06:44.050 --> 06:45.011 [SPEAKER_01]: What are you seeing? 06:45.031 --> 06:46.572 [SPEAKER_01]: And I know it's eight weeks in, right? 06:46.692 --> 06:50.476 [SPEAKER_01]: So we're sort of, you know, still getting waterboarded, so to speak. 06:51.967 --> 07:08.031 [SPEAKER_01]: you know, from a, like, a public sector sort of government standpoint, where are you seeing interest appetite, like, what conversations is the government starting to have around, you know, a generated code and sort of what that looks like for you guys. 07:08.551 --> 07:09.211 [SPEAKER_00]: Yeah, certainly. 07:09.311 --> 07:15.233 [SPEAKER_00]: So I think what we're seeing is, you know, I think the GAO came out with a report last year, and it was that roughly. 07:15.975 --> 07:37.193 [SPEAKER_00]: A, you know, $100 billion is spent on, you know, IT roughly a year and about 80% of that is on maintaining these old complex legacy code bases that, as we're moving at the, you know, of this enhanced speed that's, you know, AI is allowing us to move at the ability to interact with those, those old code bases. 07:38.154 --> 07:40.056 [SPEAKER_00]: That ends up becoming really the bottleneck. 07:40.096 --> 07:40.476 [SPEAKER_00]: And so, 07:41.973 --> 07:56.809 [SPEAKER_00]: I would say from like a product market fit standpoint, what we're seeing is just amazing alignment in terms of what blitzies offering is and then just obviously the situation that we've got ourselves in in terms of this massive estate of, 07:57.982 --> 08:06.890 [SPEAKER_00]: complex and then, you know, these code bases that people don't understand and so it's really gotten to a scale that humans alone wouldn't be able to actually work through all of that. 08:07.611 --> 08:11.454 [SPEAKER_00]: So I think AI is really the only way that we're going to be able to attack that. 08:12.195 --> 08:17.980 [SPEAKER_00]: Obviously how we do it, we think we have probably the preferred or definitely the preferred method of doing so, but. 08:19.521 --> 08:24.443 [SPEAKER_00]: It's become a problem that we have to address and AI's really the only solution at scale. 08:24.923 --> 08:37.028 [SPEAKER_00]: And so we're seeing a lot, you know, and I would say it's quite a lot easier than I would expect it to be to explain the story whenever I'm going and doing intro calls or meetings with public sector folks. 08:38.229 --> 08:41.231 [SPEAKER_00]: So, from a product standpoint on our point, that's great. 08:41.331 --> 08:42.972 [SPEAKER_00]: Obviously, there's a lot of work in the middle. 08:44.033 --> 08:55.422 [SPEAKER_00]: You know, all the stuff that you need to do, which, you know, you're obviously a pioneer for, in terms of, you know, helping companies like us get access to the public market quicker. 08:56.163 --> 08:59.666 [SPEAKER_00]: But from just like a pure product market fit standpoint, it seems to make a lot of sense. 08:59.746 --> 08:59.946 [SPEAKER_00]: Yeah. 09:00.326 --> 09:01.647 [SPEAKER_01]: And you got to it a little bit there. 09:01.787 --> 09:02.168 [SPEAKER_01]: But like, 09:02.788 --> 09:24.578 [SPEAKER_01]: You know, you're an interesting proxy sort of coming from a corporate law into, you know, sort of, a, a gentle co-generation, like, what's that learning curve been like for you and you know, you talk about sort of easy to talk about with the public, what's your experience being because I think folks listening to or you'll have folks that are maybe in a startup right now or using tooling and folks that are seeing it and they're. 09:25.278 --> 09:34.048 [SPEAKER_01]: A little icy folks all the time that are like, hey, I can see this capability, maybe I'm a little apprehensive to grab it because I'm not sure if I'm going to be able to use it the right way. 09:34.088 --> 09:37.191 [SPEAKER_01]: If I'm going to be able to understand it, people don't want to look dumb. 09:37.431 --> 09:37.591 [SPEAKER_00]: Yeah. 09:37.752 --> 09:38.613 [SPEAKER_01]: What's that been like for you? 09:38.673 --> 09:39.914 [SPEAKER_01]: You know, again eight weeks in. 09:40.074 --> 09:40.395 [SPEAKER_01]: Yeah. 09:40.895 --> 09:42.036 [SPEAKER_00]: I would say the, uh, 09:42.837 --> 09:51.202 [SPEAKER_00]: the you know the transition from doing corporate law so you know building company or helping companies structure from day one helping them raise financing. 09:52.102 --> 10:02.128 [SPEAKER_00]: You know that is completely different and there's really no overlap with what I'm doing now from talking to you you know talking to you today about context engineering and age and orchestration etc. 10:03.028 --> 10:18.421 [SPEAKER_00]: I would say there's an underlying thread which I think you and I both experienced at service academy and I think the rest of the military world does, it's just being able to figure it out on a quick timeline when things, you know, stakes are high. 10:19.482 --> 10:23.124 [SPEAKER_00]: So that's what we look for when we're hiring, you know, we're growing out our public sector team. 10:24.205 --> 10:30.968 [SPEAKER_00]: We don't necessarily need people who are our coders per se or engineers or have background in AI. 10:30.988 --> 10:34.890 [SPEAKER_00]: We're just looking for people who can figure it out at a very quick clip. 10:35.590 --> 10:40.172 [SPEAKER_00]: And now AI gives us the ability to learn so quickly. 10:41.853 --> 11:03.459 [SPEAKER_00]: you know I found that throughout my my really entire career it's like the people who can learn fast and execute on those learnings quickly and then you know have a learning loop where they're just able to iterate quickly on on those learnings that they're getting empirically or the ones that are most effective so I have that be it in the in the military in Biglaw it's again just how quickly can you get spun up. 11:04.199 --> 11:11.425 [SPEAKER_00]: And so that's what we're experiencing or I'm experiencing here at Blitzi, and then having AI to just go talk to is super helpful. 11:12.125 --> 11:16.628 [SPEAKER_00]: It's effectively anything is learnable if you... Yeah, and then it's just because of how many cheaps do you have in your pocket? 11:16.908 --> 11:18.710 [SPEAKER_00]: Yeah, and then it just becomes an effort issue. 11:18.850 --> 11:19.991 [SPEAKER_00]: Are you putting in the effort? 11:20.111 --> 11:21.251 [SPEAKER_00]: And so, that's fair. 11:21.792 --> 11:25.414 [SPEAKER_00]: Those are the people, you know, it's kind of like anything is learnable. 11:25.494 --> 11:28.957 [SPEAKER_00]: You don't actually have to ask people so many questions. 11:29.537 --> 11:32.960 [SPEAKER_00]: You can ask your copilot or whatever it may be. 11:33.620 --> 11:41.683 [SPEAKER_01]: That's how it's been and it's been super helpful and then as Blitzy sort of works, you know, pubsack and sort of broader enterprise. 11:41.743 --> 11:50.286 [SPEAKER_01]: I think one of the things I see in my careers is like new developer tools come in or, you know, new ways of developing. 11:50.927 --> 11:54.848 [SPEAKER_01]: You sometimes run into different communities of like resistance. 11:55.108 --> 11:55.328 [SPEAKER_00]: Sure. 11:55.428 --> 11:58.229 [SPEAKER_01]: I'm like, no, hey, I build this way or I build that way. 11:58.249 --> 11:59.630 [SPEAKER_01]: Or like, this is my tool chain. 11:59.890 --> 12:00.090 [SPEAKER_01]: Right. 12:00.350 --> 12:05.012 [SPEAKER_01]: How do you guys, how have you guys seen sort of reception from like the developer community? 12:05.292 --> 12:18.297 [SPEAKER_01]: And, you know, they see you guys as a threat or they see you guys as like a 10x capability that allows them to, you know, retain that human in the lead and the context and sort of the magic of that developer, but be able to go faster, what's that been like? 12:19.477 --> 12:20.378 [SPEAKER_00]: Yeah, that's a great point. 12:20.478 --> 12:27.601 [SPEAKER_00]: I think everything in AI, and especially with what we do is at a high level, a change management challenge. 12:27.641 --> 12:28.541 [SPEAKER_00]: Yeah. 12:29.337 --> 12:38.288 [SPEAKER_00]: So, you know, I think just like the, you know, the shoot from the hip experience that sometimes we see is that maybe people do see this as a threat. 12:38.328 --> 12:40.271 [SPEAKER_00]: So it's, it's incumbent upon us at Blitzian. 12:40.291 --> 12:46.459 [SPEAKER_00]: I think the, the entire community working with AI to show them that the, the, the real story is actually the 10X. 12:46.899 --> 12:52.823 [SPEAKER_00]: You know, blitzies automating 80 to 90 percent of the software development lifecycle for our software development teams. 12:53.243 --> 13:00.047 [SPEAKER_00]: But what we're doing is we're able to automate a lot of the, you know, the more manual processes that software developers didn't necessarily like. 13:00.467 --> 13:13.995 [SPEAKER_00]: So we're turning that, you know, the majority of their work into judgment, which I think is interesting and once we can kind of tell that story, you know, instead of having to be hands on the keyboard all the time, we need your knowledge to make sure that the architecture is correct, that the deployment 13:17.078 --> 13:30.792 [SPEAKER_00]: And then if we can automate 80 to 9% of that kind of middle layer of work that people don't necessarily like to do and we can give you 10x capacity, then the bottleneck at that point then becomes, you know, product design and product development. 13:31.012 --> 13:31.853 [SPEAKER_00]: And how many, you know, 13:32.564 --> 13:36.007 [SPEAKER_00]: It kind of like, what's your company's imagination and what you actually could go to do? 13:36.327 --> 13:38.089 [SPEAKER_00]: And so that's the story that we need to tell them. 13:38.149 --> 13:38.949 [SPEAKER_00]: We truly believe. 13:39.710 --> 13:45.195 [SPEAKER_00]: So we believe, I think the pessimistic case is you could see a headcount reduction. 13:45.755 --> 13:47.276 [SPEAKER_00]: I don't see that at all. 13:47.316 --> 13:51.600 [SPEAKER_00]: I see a, hey, how can we go do 10 more things? 13:51.980 --> 13:53.642 [SPEAKER_00]: And so I think that's super important. 13:53.662 --> 13:59.727 [SPEAKER_00]: And then that's also a reason why we try to get executive buy-in whenever we're doing our business development 14:00.447 --> 14:05.550 [SPEAKER_00]: Effectively, from day one, just because we know that this is a huge change in how work is done today. 14:05.570 --> 14:10.733 [SPEAKER_01]: We're sort of altering that role almost like turning a development teams into orchestration teams. 14:11.384 --> 14:12.744 [SPEAKER_00]: Yeah, I think it's a good point. 14:12.865 --> 14:13.505 [SPEAKER_01]: Yeah, exactly. 14:13.545 --> 14:15.085 [SPEAKER_01]: That's super cool. 14:15.345 --> 14:28.610 [SPEAKER_01]: You know, as you look out now, sort of in public, you know, at sort of a a well-known, sort of well-funded to your point, like, really cool first of its kind of kind of company, how do you think about sort of like building that team out? 14:29.030 --> 14:32.891 [SPEAKER_01]: How do you think about, you know, where do you see maybe opportunity? 14:32.971 --> 14:35.152 [SPEAKER_01]: Not to say, hey, show me your playbook, but 14:35.792 --> 14:42.679 [SPEAKER_01]: You know, folks are going to be listening, who we're going to say, hey, either I want to be on that team that sounds awesome for sure or be maybe in the government. 14:42.699 --> 14:44.180 [SPEAKER_01]: They're like, hey, I can probably use that. 14:44.220 --> 14:45.641 [SPEAKER_01]: Like, how are you thinking about that whole? 14:46.397 --> 14:48.618 [SPEAKER_01]: build and then go implement and execute. 14:48.938 --> 14:49.338 [SPEAKER_00]: Certainly. 14:50.799 --> 14:56.921 [SPEAKER_00]: So, Blitzi at a score is a language agnostic, use case agnostic, autonomous software development platform. 14:56.961 --> 15:10.986 [SPEAKER_00]: So, I think something that we have to really focus on on the pubsac is that because that, you know, because that is so widespread, you know, we could effectively attack any use case as long as software is the medium of what we're talking about. 15:12.514 --> 15:15.376 [SPEAKER_00]: and obviously there's so many opportunities where that makes good and bad. 15:15.536 --> 15:16.758 [SPEAKER_00]: That's kind of bad. 15:16.878 --> 15:19.580 [SPEAKER_00]: So we could be a little bit of paralyzed by choice. 15:19.600 --> 15:20.381 [SPEAKER_00]: Yeah. 15:20.561 --> 15:27.767 [SPEAKER_00]: And so that means that we have to be extra targeted and how we're spending our bandwidth because obviously as you know, and I think everyone degree that's. 15:28.207 --> 15:53.768 [SPEAKER_00]: it's super important where you spend your time is actually where you make the progress and so we're bringing on a full stack sales team so we're looking for you know industry sales leaders sales leader plus multiple you know strategic account executives who have really great experience within this entire industry you know I think we have we have quite a few athletes kind of 15:56.410 --> 16:11.368 [SPEAKER_00]: do most things but especially in this sector we need people who you just can't replicate you can't replicate experience which is super important in this industry as I'm sure you probably agree with and so we're looking for for industry veterans 16:12.870 --> 16:36.193 [SPEAKER_00]: people who do have the athletic capability to effectively do anything because we still have the the scrappy nature of a startup, although we are well funded and have the capability to go effectively do things that we think make sense from a NPV perspective, but we still need people who can context switch and be very dynamic and so that's what we're looking for now and I would say on the government side, you know, if you 16:37.178 --> 16:40.702 [SPEAKER_00]: for people who are looking at, let's see them wondering if we could address their issues. 16:41.924 --> 16:45.148 [SPEAKER_00]: We really start differentiating ourselves at scale. 16:45.208 --> 16:51.576 [SPEAKER_00]: So, you know, think 500k in terms of a code base estate to work against. 16:51.636 --> 16:52.176 [SPEAKER_00]: That's, that's, 16:52.857 --> 17:14.025 [SPEAKER_00]: that in above is where we really start showing our differentiation and there's definitely a lot of that within the government space and so I would say we're open for all problems, problems sets that we could go execute against, but we again have to be very targeted and then we're also breaking it up, it's not necessarily just federal defense, we're looking at 17:14.555 --> 17:15.897 [SPEAKER_00]: state local and education. 17:15.937 --> 17:21.044 [SPEAKER_00]: I think there's, you know, massive media there as well as federal civilian and then federal defense. 17:21.104 --> 17:30.557 [SPEAKER_00]: So really trying to have a widespread view while being targeted within each one of those verticals on the, you know, the opportunities that make them a sense. 17:31.167 --> 17:35.630 [SPEAKER_01]: Yeah, I think a state and local sort of sledvert is super interesting. 17:35.690 --> 17:38.252 [SPEAKER_01]: I think it's historically just underserved, right? 17:38.773 --> 17:51.602 [SPEAKER_01]: And folks look at it and they're like, well, it's two sort of disparate or it's two maybe fractured segmented, but especially when you use sort of that legacy example, 17:52.503 --> 17:54.583 [SPEAKER_01]: the degree of transferability. 17:55.184 --> 17:56.724 [SPEAKER_01]: It's pretty intense. 17:56.904 --> 17:57.864 [SPEAKER_01]: Pretty intense. 17:57.904 --> 18:07.426 [SPEAKER_00]: I think that fragmentation and federation of that whole sled space also makes the, you know, the use case even more actually interesting. 18:08.106 --> 18:16.028 [SPEAKER_00]: Just in terms of everything's moving towards integration and you need a lot of, you know, if you're using a very old, you know, codebase from, you know, 18:16.568 --> 18:19.869 [SPEAKER_00]: state x and it needs to integrate with another sloppy disc up load. 18:19.989 --> 18:23.690 [SPEAKER_00]: Yeah, so I see it as a pretty right space feeling. 18:23.730 --> 18:25.050 [SPEAKER_01]: Yeah. 18:25.750 --> 18:31.531 [SPEAKER_01]: How do you think about or maybe, you know, how do you think about like, you know, let's use like state and local as an example. 18:31.551 --> 18:43.594 [SPEAKER_01]: I think historically whether whether actual or just they have a rep, there's a rep for, hey, there's sort of underserved, hey, there may be like ultra to your point federated legacy, you know, 18:45.434 --> 18:53.575 [SPEAKER_01]: Vendor engagement, knowledge transfer going, how do you help going back to the change management exercise that's something like this is? 18:53.655 --> 19:01.157 [SPEAKER_01]: How do you help build that awareness and that adoption and that understanding and almost do that education and knowledge transfer? 19:01.837 --> 19:02.917 [SPEAKER_01]: How do you guys think about that? 19:04.017 --> 19:11.139 [SPEAKER_01]: Could I think when people hear AI and code, they're like, oh, it's a sky net, and you know, it's not sky net, right? 19:11.419 --> 19:13.179 [SPEAKER_00]: Yeah, how do you sort of meet them where they are? 19:14.028 --> 19:15.629 [SPEAKER_00]: Well, I think that's exactly it. 19:15.649 --> 19:17.149 [SPEAKER_00]: And I think that's super important. 19:17.169 --> 19:28.213 [SPEAKER_00]: I think flashy AI startups and startups in general get a bad rap of having the vibe of like, hey, come to us and we'll tell you how great we are. 19:28.693 --> 19:39.237 [SPEAKER_00]: And how you should adopt us instead of actually going to the end user's environment and really integrating with them and knowing their problem sets. 19:39.657 --> 19:39.857 [SPEAKER_00]: And so 19:40.337 --> 19:48.581 [SPEAKER_00]: And I don't think this is an area where I can help, I think this is just like manual elbow grease for you actually to get out and meet the people, understand them. 19:48.601 --> 19:53.463 [SPEAKER_00]: We've talked about, and this is still on my roadmap to figure out and to do, and I think it makes sense. 19:53.483 --> 20:02.967 [SPEAKER_00]: But there's a community of, you know, I think of the state and local level, CIOs, tech leaders within those organizations. 20:02.987 --> 20:08.070 [SPEAKER_00]: They have very similar problems that's although specific to their region and their state. 20:09.030 --> 20:20.337 [SPEAKER_00]: issues that they're dealing with, but creating some type of community, you know, we've actually seen that some, you know, there's like a really strong kind of conference, you know, connection between all of these, those type of leaders. 20:20.717 --> 20:27.962 [SPEAKER_00]: And so, you know, making sure that we go to those conferences, making sure that we engage with them, but then also having specific programming for them, where we can actually, like, 20:28.162 --> 20:30.645 [SPEAKER_00]: offer things without ever engaging. 20:31.666 --> 20:33.348 [SPEAKER_00]: That's one way that we're trying to do it. 20:33.408 --> 20:40.677 [SPEAKER_00]: But ultimately, you just have to go and you just have to actually care and do the hard work of understanding their issues. 20:41.878 --> 20:43.480 [SPEAKER_01]: All right, two last questions. 20:45.320 --> 20:46.661 [SPEAKER_01]: Amy, a curveball, I don't think so. 20:46.681 --> 20:48.242 [SPEAKER_01]: Oh, it's pretty baseball. 20:48.302 --> 20:49.323 [SPEAKER_01]: Yeah. 20:50.083 --> 20:53.126 [SPEAKER_01]: So put back your sort of like intel officer hat on. 20:53.226 --> 20:53.426 [SPEAKER_01]: Right? 20:53.446 --> 20:57.469 [SPEAKER_01]: Like using that sort of persona, like, what could you have done? 20:57.489 --> 20:58.449 [SPEAKER_01]: It would blitz you back then. 21:00.411 --> 21:01.552 [SPEAKER_00]: That's actually super interesting. 21:01.592 --> 21:02.672 [SPEAKER_00]: And this wasn't a plant. 21:02.772 --> 21:03.573 [SPEAKER_00]: Yeah. 21:03.593 --> 21:04.153 [SPEAKER_00]: Definitely wasn't. 21:04.173 --> 21:05.915 [SPEAKER_01]: So I was like, wait, I might be going on. 21:05.955 --> 21:07.095 [SPEAKER_00]: This wasn't a plant. 21:07.910 --> 21:13.135 [SPEAKER_00]: So actually what got me interested in defense tech and, you know, innovation and software whatnot. 21:13.475 --> 21:18.179 [SPEAKER_00]: So I don't have any background in this, obviously, I study economics, I talk economics. 21:18.359 --> 21:19.300 [SPEAKER_01]: I'm an e-commagitive. 21:19.500 --> 21:20.241 [SPEAKER_01]: Awesome. 21:20.301 --> 21:21.482 [SPEAKER_00]: Yeah. 21:21.923 --> 21:27.408 [SPEAKER_00]: So I was, I was deployed to Iraq 2016, 2017 timeframe. 21:27.468 --> 21:31.171 [SPEAKER_00]: I was, I was doing a light ISR mission with special forces. 21:32.492 --> 22:00.238 [SPEAKER_00]: I was in charge of an Intel operation and we there was just a tactic that we were doing that involved Excel in a very like clunky way and you know it was very obvious like you know when that when the hair starts standing up on your opening neck to be like this is so inefficient there must be a better way Yep and so I just took it on to be kind of a pet project during that deployment to teach myself enough Python to figure out some type of solution that we could do 22:01.479 --> 22:08.603 [SPEAKER_00]: And I don't know if it was very good, but I worked, I ended up creating something and ended up being kind of tested downrange, which was interesting. 22:08.643 --> 22:16.648 [SPEAKER_00]: But like figuring out, first up, I thought it was weird that I had to figure it out as like an intel guy with the e-com background. 22:17.568 --> 22:23.592 [SPEAKER_00]: The amount of work that it took to even like get it tested, it goes back to all the things that, you know, you talk about frequently just, 22:24.032 --> 22:27.356 [SPEAKER_00]: trying to put Python on a secure computer and get it tested. 22:29.118 --> 22:30.779 [SPEAKER_00]: It took some heat for that. 22:32.201 --> 22:34.884 [SPEAKER_00]: In any event, I just became very... 22:35.485 --> 22:46.696 [SPEAKER_00]: kind of passionate and understood that a software defined Intel community and just military operational process in general is going to be super important going forward. 22:47.797 --> 22:54.704 [SPEAKER_00]: And so that honestly spurred my interest in going to places like DEIU and getting involved in the innovation ecosystem involved in the 22:55.325 --> 23:01.930 [SPEAKER_00]: you know, how can we get non-defense contractors on contract quicker and you know, all of the all of the work that that I think you're spearheading as well. 23:01.990 --> 23:04.772 [SPEAKER_00]: So, um, what could Intel do if let's see? 23:04.912 --> 23:08.415 [SPEAKER_00]: Yeah, I mean, I think it could, you could do massive amounts of things and transport. 23:08.695 --> 23:15.160 [SPEAKER_00]: And that's why I'm also super excited to bring into the Intel community as well, because that's just obviously like near to my background. 23:15.180 --> 23:15.421 [SPEAKER_00]: Like yeah. 23:15.881 --> 23:16.081 [SPEAKER_01]: Yeah. 23:16.421 --> 23:17.062 [SPEAKER_00]: Do that's awesome. 23:17.182 --> 23:17.422 [SPEAKER_01]: All right. 23:17.782 --> 23:20.945 [SPEAKER_01]: Um, last question before I go to my final final. 23:22.548 --> 23:46.153 [SPEAKER_01]: I always ask folks who've like, you know, made job transitions both out of a uniform and then sort of new role like what sort of surprised you the most You know, you come and you can answer it in either way right from Air Force out through school and into big law Yeah, and then from sort of big law into fast startup I think all of us have ideas on what you know the grass looks really green over there and you get over you It's a little different. 23:46.273 --> 23:47.473 [SPEAKER_01]: Yeah, what's the price you? 23:49.147 --> 23:58.430 [SPEAKER_00]: I would say I think coming out of a service academy, but then also just the military in general, because we do have such differentiated experience. 23:58.510 --> 24:03.152 [SPEAKER_00]: I think there is a, there's an as, like a tacit assumption that when we separate. 24:03.592 --> 24:08.097 [SPEAKER_00]: that we're going to have tons of opportunities to continue. 24:08.337 --> 24:09.559 [SPEAKER_00]: Yeah. 24:09.999 --> 24:14.344 [SPEAKER_00]: And I think everything that we did give us a great foundation and it can open doors. 24:14.824 --> 24:19.569 [SPEAKER_00]: But if you sit idly, like nobody is going to be, you know, coming out to find you to 24:21.102 --> 24:22.623 [SPEAKER_00]: for lack of their term, nobody really cares. 24:22.643 --> 24:24.364 [SPEAKER_00]: Like you still have to make people care. 24:25.104 --> 24:29.306 [SPEAKER_00]: And so the whole background is a great door opener, but you still have to execute on it. 24:29.386 --> 24:31.968 [SPEAKER_00]: You still have to hustle to make things happen. 24:32.708 --> 24:35.009 [SPEAKER_00]: You know, I've heard this from senior leaders as well. 24:35.029 --> 24:40.092 [SPEAKER_00]: And so I think, you know, I got out as a captain, but I think it goes across the board. 24:40.732 --> 24:46.255 [SPEAKER_00]: And so I think that's probably the biggest one that you still, like the hustle never really stops and you just have to keep pushing. 24:48.417 --> 24:49.857 [SPEAKER_00]: That would probably be my biggest takeaway. 24:52.128 --> 25:02.404 [SPEAKER_00]: I guess even, you know, I like had done, you know, some, I think some things that were respected in industry, like working in Big Law, you know, generally respected, but when I get to Blitzy, nobody really cares. 25:03.046 --> 25:05.247 [SPEAKER_00]: It's actually hard. 25:05.307 --> 25:06.768 [SPEAKER_00]: And that's how it should be. 25:07.608 --> 25:10.610 [SPEAKER_00]: Every time you go somewhere near you, you have to prove yourself and you have to make yourself useful. 25:10.650 --> 25:14.952 [SPEAKER_00]: And then whatever you can provide, that's going to be the value that you're doing at that point. 25:15.572 --> 25:16.472 [SPEAKER_01]: I think it's a change in teams. 25:16.492 --> 25:17.693 [SPEAKER_01]: There's an athlete, right? 25:17.833 --> 25:19.054 [SPEAKER_01]: No one cares that you won. 25:19.274 --> 25:21.615 [SPEAKER_01]: We go with him last year. 25:21.655 --> 25:22.195 [SPEAKER_01]: We do it now. 25:24.953 --> 25:28.935 [SPEAKER_01]: All right, last question, I asked this one to sort of everybody as a wrap up. 25:29.195 --> 25:29.335 [UNKNOWN]: Yeah. 25:29.636 --> 25:31.076 [SPEAKER_01]: I'll give you content like you can go. 25:31.136 --> 25:38.861 [SPEAKER_01]: It's gone in every direction possible to like, I would change sort of like fast food, I would change congressional policy and everything in between. 25:38.881 --> 25:45.364 [SPEAKER_01]: But you're king for a day, you've sort of got the magic wand, you can make a decree and sort of change one thing. 25:45.764 --> 25:46.665 [SPEAKER_01]: What do you change in why? 25:48.723 --> 25:50.564 [SPEAKER_00]: So I fly a lot with Blitzie. 25:50.684 --> 25:53.345 [SPEAKER_00]: I'm going back and forth between coasts most weeks. 25:53.845 --> 25:55.706 [SPEAKER_00]: And so that's kind of a joke. 25:55.726 --> 25:59.848 [SPEAKER_00]: Like I would not have seats to be reclineable on airplanes. 26:00.208 --> 26:00.689 [SPEAKER_01]: Ooh. 26:01.969 --> 26:03.030 [SPEAKER_00]: Because I'm just working so much. 26:03.070 --> 26:05.231 [SPEAKER_00]: And then when I work in there, I guess land in the way. 26:05.271 --> 26:06.291 [SPEAKER_00]: Yeah. 26:06.451 --> 26:08.953 [SPEAKER_00]: No, that's not really what it would be. 26:09.073 --> 26:14.015 [SPEAKER_00]: I think it goes back to what I was talking about with my experience downrange, trying to create software. 26:14.875 --> 26:17.517 [SPEAKER_00]: And it's obviously like very unbranded or discussion, 26:18.738 --> 26:39.056 [SPEAKER_00]: You know, if I could be a king for a day, it would just be, um, and maybe it's a boring answer, but it's just like accelerating the work that the people, you know, entities like second front, uh, are doing, that we are doing, but DIU is doing, you know, I think we're getting there, we're getting closer, um, but just making it such that we can get a new capability to the force 26:39.777 --> 26:41.538 [SPEAKER_00]: You know, we needed it a step. 26:41.618 --> 26:44.840 [SPEAKER_00]: So if we could do it, it's such an important time right now. 26:44.960 --> 26:46.721 [SPEAKER_00]: That would be yeah, that would be amazing. 26:46.741 --> 26:48.763 [SPEAKER_00]: And I think it helps with our competitiveness. 26:48.883 --> 26:57.448 [SPEAKER_00]: Obviously, it helps with, you know, hydrating our defense tech community and how we interact with the community like that. 26:58.969 --> 27:09.697 [SPEAKER_00]: Right because if you people they want to have they want to see and they want to have like a loop where they're actually doing something and then it's being implemented and then they're they're excited and how to know that. 27:09.857 --> 27:19.524 [SPEAKER_00]: Yeah, you know, like I think we lose tons and tons of talent to the fact that you know people want to see return on their investment other time and work and so. 27:19.884 --> 27:22.647 [SPEAKER_00]: to the extent we can make the flywheel quicker, obviously. 27:23.227 --> 27:30.074 [SPEAKER_00]: It's something that we'll talk about, but I would say like compress the T even 30 this because we needed it, you know, ASAP. 27:30.314 --> 27:31.455 [SPEAKER_00]: So I think that's important. 27:31.475 --> 27:35.138 [SPEAKER_00]: And then, yeah, I also, I just don't like it when people reply their seats. 27:35.278 --> 27:37.540 [SPEAKER_01]: Yeah, I like that that's funny. 27:37.861 --> 27:39.522 [SPEAKER_01]: Dude, this is awesome. 27:39.702 --> 27:44.347 [SPEAKER_01]: I mean, for super exciting, we were able to get it made super jazz by what you guys and the team were doing. 27:46.017 --> 27:47.077 [SPEAKER_01]: folks that want to learn more. 27:47.857 --> 27:52.158 [SPEAKER_01]: Go to blitzie.com, go to LinkedIn, hit jobs, all other things. 27:52.418 --> 27:54.699 [SPEAKER_01]: Cool jobs, cool tech, cool opportunity. 27:55.219 --> 27:56.539 [SPEAKER_01]: Sort of get it on the ground floor. 27:56.719 --> 27:57.319 [SPEAKER_01]: So to speak. 27:57.479 --> 27:58.220 [SPEAKER_01]: Yeah, exactly. 27:58.320 --> 28:00.760 [SPEAKER_00]: I got about 170 employees right now. 28:00.780 --> 28:02.300 [SPEAKER_00]: We're scaling as quick as we can. 28:02.340 --> 28:02.720 [SPEAKER_00]: Heck yeah. 28:03.101 --> 28:05.121 [SPEAKER_00]: Um, so, so come join the team. 28:05.441 --> 28:05.781 [SPEAKER_01]: Oh, yeah. 28:05.861 --> 28:06.901 [SPEAKER_01]: Dude, thanks for swinging by man. 28:06.921 --> 28:07.501 [SPEAKER_00]: This was awesome. 28:07.521 --> 28:08.082 [SPEAKER_00]: Appreciate it. 28:08.302 --> 28:08.522 [SPEAKER_00]: Thanks. 28:08.802 --> 28:09.002 [SPEAKER_01]: Thanks. 28:09.022 --> 28:09.742 [SPEAKER_01]: Check it in everybody. 28:09.782 --> 28:10.022 [SPEAKER_01]: Cheers.