of a lot of where I got today was, a lot of hard work. A lot of putting in the hours to get there. And then, schooling on top of that to kind of lead me in that direction. It's It's been, probably 15 years, and I had to kind of start out, early on tech support type stuff. And i kind of worked my way up and, expand my knowledge base. And then went up and up then obviously, just like I said, putting in the hours and taken every opportunity to learn something new.

um, so, I mean, what what I do now is, you know, in Dev Ops is really, um the kind of the the middle point in getting software, um, out to, you know, production site. Um, what we do is, um, kind of Ah, um asset management software. So we you know, we have to take everything from the developers making, you know, creating the code to pushing it through kind of release gates or staging gates so that, you know, we could get some q and stuff on it. And then, um you know, once that's passed, then we get it out. Teoh production. So the ah, the You know, the hours air kind of sometimes odd because, you know, typically, we want to do kind of like a no downtime deployment type thing. Um, so that, you know, usually involves doing it, you know, like, 10 o'clock at night. Um, just just that we don't impact our customers. Um, so it is a little bit different. We Ah, you know, sometimes you know, you'll you'll, you know, come into the office and and, you know, like, 10 o'clock in the morning and and leave it like, three o'clock in the afternoon just so that you can get home and then prepare for, ah, software released later that night, which may take an hour to, you know, later on the evening. Um, other times, you know where there's ah, you know, there's issues going on and customers are having problems than you know. Sometimes it's a 10 hour day, so it really, really varies in, You know, that kind of, you know, aspect as faras hours worked or weekly, it's it's never the same. It's it's always different, depending on what's going on.

I mean, there's a lot of challenges. There's a lot of, um, you know, in the Dev ops role, we're kind of like I said, the middleman between, um, you know, the developers and, um, the customers and the challenges are there that you know, developers, um, you know, kind of do things their way, and they understand their aspect of their job, but they don't understand the aspect of other people's jobs. So, um, being in the middle, you know, you kind of have to speak both languages, so to speak, um, and get, you know, get those guys, um kind of, you know, in sync together so that we all know what's going on. Um, so that's that's kind of a big challenge in The Dev Ops world, because you do have to be able to speak both those languages and speak to both those types of people, um, so that we can get, you know, kind of everybody in sync. And if there's a problem, um, you know developers or typically well, it's it's working in my environment. Well, it's not working here, so let's let's find out why it's not working there. Um and then just you know, pushing through those challenges because, you know, oftentimes, you know, on the other end, customer will report something I'm an issue with, you know, with the software, the with the product. Um, and they don't you know, they're not. They're not technical people. Usually they're just saying, Hey, I'm getting an error, and then we have to kind of decipher that error. Um, you know, on the Dev upside. And then push that back to our development team so they can kind of go. Oh, OK. You know, now I see what's going on, because when the customer reported there's no really good information there, so