I got my start in technology in the military. I was trained electron ICS technician in the U. S. Navy and I worked on radar and a mainframe computer system. It was called the snap to It was a supply computer, and it had a four megabyte hard drive record like the record. It was very large. And, um and then it was quite a few years before I got back in the technology because the Internet wasn't here yet. And so, um, and around 95 or so, I got a job with a company called Stream that supported a company called Comp you, sir, which was a lot like a A. Well, some people may not have heard of CompuServe and I did phone support, and it was basically helping get people on the Internet. And from there I was just kind of self taught because there wasn't they weren't really teaching Web technologies in school yet, and there was only about 256 colors online, maybe, and, um, and that had a high aptitude for it. So I was able to kind of build a career around, um around computers and technology by just learning it on my own

um before before the virus, I was usually working and I'd be in an office. You know, sometimes there would be work from home. And, um, but most of time that would be in an office. And so I mean, I have traveled for work of incent places, and, um, it's ah, in the New York City in London on jobs. So that's been pretty wonderful at times. And then at other times, you know, it's not that great, but, um, but for the most part, it's been pretty good.

see, I've been a lamp stack, Um, engineer and the lamp stack is Lennox Apache, my sequel and PHP, and it's used for a platform called Ripple Andrew Pols, an open source platform that I've been. It's been kind of a niche for me, and, uh, so that's been primarily my bread and butter. But more recently I've been involved in de Box, and that's employment methodologies for the cloud. And there's a lot of tools in the Dev ops environments. Some of those tools air ah, terra form. There's a company called Hash E Corp that has a number of these tools terra form and vagrants and and, um, Packer. They're used for, um, for building infrastructure environments with infrastructures code, which is a methodology that, um, is used to produce what you would call an immutable stack in the cloud. And I guess the best way to explain it is back in the day you had, um, you had servers and stuff that she would be deploying to. And when you had to facilitate putting co changes on those servers, there was a lot of things you had to do. Um, because you weren't You weren't building something virtualized. So now we have a virtualized environments like you can emulate an environment I can emulate. I can run a Lennox machine on my Windows machine or my Macintosh machine while that operating systems running like like having two operating systems. Well, that means that the Lennox server or the Lennox operating system candy can be deployed from a code base. And if you can deploy from a code base, that means that every time you make a change, you build that code base from the very beginning. So I'm not applying a code changed, too, Um, a running operating system. So So when the coat comes online, it's just like it was when he built it the first time. And so it allows you to, um, to deploy with regularity and not have to worry about some of the effects of code changes. For one, you can build and test this this operating system or this code deployment completely from end to end. And that's what we call immutable effort concept in the methodologies of development to implement operations