eso a little bit of of my story. Um, really quickly. You know, when you're in high school and you're trying to figure out what do you wanna do, where you wanna go in college and all that stuff? All my friends seemed to have to figure it out. They all wanted. I'm gonna be an architect. I'm gonna be an engineer, and I really didn't know what I was gonna do. And but my dad was a c p A. So I decided, while I just do what my dad does and to be fair, growing up my chores Where Doing taxes with my dad. So when I came to go to college, I figured I would just be an accountant like him. Um, So I did that, and I really I really hated it. It wasn't for me. I don't think I have the personality for it. It just didn't jive. Well, so I was looking for other things, uh, to do, and I stumbled upon coding. I remember going to code academy and opening up HTM l and I coding my first html page and I fell in love. I didn't know that this waas um option for me. And so that's the beginning. And I didn't have any developer friends growing up, so I genuinely didn't know this was an option. So that's the beginning that led me into development, and I'm just, like, truly in love with it.

my responsibilities are I basically build the core product of the current company that I am in. I am responsible for building all the a p I n points all basically all the functionality off the core product. So that's my responsibilities on a higher level. Um, the priorities are, you know, we are start ups. So there is a sense of urgency when building these things, and there are expectations that need to be met with stakeholders. And so those are their priorities. Pain points. I don't have many. I've been doing this a long time. I feel very comfortable. Uh, and a high paced environment, though I would not consider this a high paced environment. So I'm very comfortable in this. Ah, pain point might be a lack of information that I need at the moment to execute, and the only pain, if you can even call it that is having to, like, go fetch that information, which it's not a big deal. So it's hard for me to describe a specific take place and strategies in dealing with challenges. I would say that I would have I have guidelines in place that helped me fall back on these guidelines in case on day for me to know that I'm doing a good job and I'm meeting expectations that I set for myself.

so tools. I would say eso I use an e. You know, uh, that's basically where I live. I live in V s code. I have it set up for Go Lang. So that's the language. The programming language that we use, Um uh way also have jealous grip on the front end. And I'm well versed in that as well. So I'm able to jump from one side to the other. Uh, in terms of algorithms, there aren't any specific algorithms that I can point to that we use. And the models are just defined by our product. But that s so there's no specific models I could say. So that's it, for the most part.