I would definitely say so. I had a very, very interesting experience at both companies. And I'm really grateful that I got the opportunity to work there. I, in some ways, again, I think part of it has just influenced me to stay in the industry because I, again, I spent time in this industry where everyone there is there because they really want to be there. So I think just by itself, that was huge in kind of shaping the rest of my career direction and my career preferences. And then I definitely learned an enormous amount at both companies. I spend most of my time there as a systems integration and test engineer in a couple of different capacities. And, you know, you really don't learn a whole lot about test engineering, and integration at the undergrad level, I got some of that through some of the project teams that I was involved with, definitely the MIT Rocket Team was a very useful experience for me, but I really had to learn a lot of the fundamentals behind that on the job. And I think that was hugely valuable in helping me understand, okay, you know, there's the design end and that's what you spend a lot of time studying in engineering school. And then there's all of that meeting reality, which is integration and test, which is, how do you even develop a testbed for something that is going to operate in conditions that do not exist on Earth? How do you convince yourself that you've built the right thing, and that you built the thing right when you have to navigate a fundamentally unrealistic test condition? And what do you even need to test? What can you reassure yourself is going to work without having to do that? And I think my five years were really just an education in how do you make something that you've designed actually work in this very messy, imperfect, real environment. So that was kind of a key thing that I took out of that. And then I do have to say, I really appreciate, both at SpaceX and JPL, I worked on some very, very cool, very complex projects that required hundreds, if not thousands, of people to work on them for years. And something that I found just absolutely fascinating is you've got a lot of brilliant people and no one person understands the whole system. It's not possible. It's too complex. And given that, the corollary to that is that everybody has a very different idea of what it is that system does. And I that really got me thinking a lot about how is it that all of these people have a different idea, and yet, you know, they're all kind of pulling in the same direction such that your net result in force is, you know, in most cases up, so I that's really a people problem and a lot of systems problems, I learned, sometimes the hard way, they're are people problems, their differences and understandings and assumptions and risk stances. And ultimately, I think that's what led me to pursue the LGO program, because it included the MBA, because it really stretched me ultimately, in thinking about how, how people work together, and how that affects technical projects. We have an idea that technical projects are cold and emotionless. And they are absolutely not. They are built by squishy humans, and we build all of our squishy human assumptions into them. So yeah, I'm glad that I spent a lot of time kind of learning about moving things into reality. And the reality of having human beings develop things. That was really, really valuable to me. And I think it helps me really get the most out of my education. It's part of the reason that as you mentioned, JMill, I pursued the Aerospace Innovation Certificate during my grad program