s o I. I started programming in high school. Ah, I had I went high school in a very rural community, actually, but it just happened tohave Ah, a woman who taught ah, programming class. And so I took a bunch of programming classes my junior year and really liked it. Um, and once I got out of high school, I sort of floundered through some college courses, but I didn't do very well. Um, and then eventually, I ended up getting a programming job. Um uh, doing like, really basic web design. This would have been in, like, 1999 or so. So the web was pretty fresh. Um, and I did that for a few years. And then I got an internship with a company doing video surveillance. Um, and that that that job, that job was kind of where I really started programming quite a bit on. That kind of became my career path ended up going back to school. When I was older, I was about 28 when I went back to get a degree. Um, and then once I got my degree. I've just been programming ever since then, So I had kind of a strange arc through through university, so I think

I'll start with the weekly work hours. First, I usually put in about a 40 some weak storm or some weeks or less, but I'd say I probably average about a 40 hour work week in my current role. I don't travel, Uh, and I am free to work from home whenever I feel like my employer doesn't care when or how I get my job done, only that I deliver on the things that I've committed to, um as's faras the responsibilities and decisions. Um, that's a That's a really broad question. I mean, I'm responsible for for basically keeping our existing services running, making sure things are running smoothly, making sure that performance adding new features. Responding to customer issues responding to bugs that are filed by our Q A collaborating with other parts of the business, too, Um, basically to broadly meet customer needs. So, um so that the responsibilities are definitely above and beyond just just programming. There's also an aspect of being a professional and working in that setting

That's a really interesting question. So currently we use, um we're basically most of the code we write Isn't pipe on our JavaScript? Uh, the frameworks on the front end? It might be angular. React on the back end. There's a lot of were we used Django on the back end and then post presses a data store in addition to a bunch of Amazon AWS stuff. But I think the better answer to this question is, uh, you my expectation for new developers with whom I work is that they can learn a technology that they need, that they need to know. And they're comfortable exploring new technologies and branching out into other things we don't hire on the basis of technology. So I've hired multiple developers that have never written a line of python in their life on That's deliberate. We don't We don't hire on the basis of what people know. We hire on there on the basis of their ability to learn. Basically