so kind of answer that first question, How did I get to where I am? Today was just the boot camp before I went through Dead Mountain. I was working in tech. Andi, like I t support just like help desk stuff and getting into the boot camp. Actually, for me at least, was a little bit of an accident. My two best friends applied for the boot camp and didn't make it in. And so I figured I would just, you know, I have been kind of thinking in in I t use a lot of tech tools and I had kind of kind of the conclusion that I wanted to build the tools instead of just using them on dso with my two friends trying to get into Debt Mountain. They both got denied they were quite rejected. And so I was like, Well, I want to do this anyway, I might as well just see if anything comes of it. So I applied for it just to kind of help them feel better that they didn't get rejected. I didn't think I was gonna get accepted. And then I did, um so I kind of went from and I think it was probably just because I had already been working in tech. And so I kind of understood, you know, basic stuff like the S I layer and networking protocols and stuff like that. And so I was thinking tech like that. I got I got accepted into the boot camp, and then I just get it. And now I here I am, soum So, like I said, I was in tech already. Um, in about 2000 14 or 2013. 2014, I started working tech support for a local Internet service provider, Andi. It was really scrappy. I mean, we were doing everything via Tell Net, you know, we would remote. It was it was wireless. Five g internet. And so we were We would have to remote into the, um into the receivers on people's houses. And we were using telnet and then running all sorts of bashed scripts to kind of troubleshoot stuff and make it work, make it work. And so I kind of just I don't know, I kind of fell in love with the romanticism of doing stuff via the terminal. And, you know, we would learn. I learned a bunch of stuff like how to watch Star Wars asking Star Wars through telling it. I don't know if that was a kind of a common thing for me with my team. Just kind of like those quirky tech things. Um and then, yeah, I just kind of escalated from there. I moved on Thio. I worked tech support for a nice car VoIP provider. And so, you know, working with the I T managers as at different businesses. And if their phones went down, I would just have to remote into their network and kind of figure out what was going on. Um, as far as learning about Dev Mountain on my team at that company was called the hip tell the one where I supported VoIP Systems. There were a couple of people on the team, so the team lead had his bachelor's degree in computer science on do a lot about programming and networking, and so I would I would watch him. You know, he kind of did all the database stuff, and I think that he supported our website, but I'm not positive. But he did a lot of stuff in, like PHP and SQL, and so I would watch him sometimes when he got these tickets to fix people's databases, and I was just fascinated, just like, Wow, you're just like setting off this stuff up with your brain That's so cool on There was another guy who had gone through Newmont University, which is like an accelerated bachelor's bachelor's degree program. Um and yeah, I just always thought it was super fascinating that they were able to just create stuff out of thin air. I thought it was amazing. And, um so I kind of had done a little bit of research about, like, how do I get into this? And I looked into stuff like free code camp and whatever. I didn't really want to go to school, because in between these two jobs, I had done a little bit of schooling A to a local university. And I didn't want to go into debt. I didn't want to go into student debt. I was kind of a little pansy. Didn't wanna didn't want to take on that debt on dso. I was like, How could I do this? Where is cheapest? Possible as fast as possible because I also have my family to think about like I can't just take years off of working Thio put myself through school. Um, but yeah, learning about the boot camp really was these two best friends of mine who one of them was like, he has always been into tech, but I don't know why he didn't get in, but he kind of had a friend who went through Dev Mountain and also started Lambda School. Um and so he was like, Yeah, I'll go through Dead Mountain. Whatever. And he told me and my other friend about it, and we just kind of all decided Thio apply at the same time.

at guide c x I am on the back end. Our stack is ruby on rails where the post crest database and then the front end is react. Um on it's all driven by graphic ul So on the back end, we're doing rails with graphic UL on were used docker Um and it's pretty Jinky I don't really like rails is the first time I've had experience with Ruby and I'm not super impressed. Uh, but a sfar assed decisions, you know, we were making the jump from rails over to note We're gonna do notes, note and express on Ben were also when it's more mature, we're gonna try out Dino because we all love typescript. Um, it's a really small team. So the decision is pretty much all of the decisions are made. Um, we're all involved. Recently, I just stood up the first note service. We're doing micro services. So I just put up the first note authentication service, which was really cool. I've also I've have experience with bash, and so I've also automated a lot of our initialization because when I first came onto the team getting the repo cloning the repo down from get hub and then installing all the dependencies. It was just this huge mess. It was super clunky. And so I wrote a bash script kind of automate all of that. So I've done that. We're all also really involved with hiring because we wanna maintain our culture as long as possible. There were still in start up mode, and so we're afraid of moving into that kind of small, medium sized business where you might its possible to lose your culture that close, tight knit. Everybody's a family culture. And so we're all involved in hiring just to make sure that that kind of stays the same. So I'd say top three priorities. I mean, obviously writing code, um, hiring. And then we're kind of making all these decisions about, like, code cleanliness and what our style is and kind of making those type decisions Top three pain points. We work with A with a, um, outsource step team. So the way I had sex was born was this Our CEO Pete had this idea, and he contacted with this outsource step team who built the first iteration of the product. And then when it started making money, he was like, Okay, I'm gonna hire my own Deb. So he hired my manager, Who is Hey was the first Internal Dev, and now they're building out the team. But we still work with that contract ID Dev team. So now that we're kind of building our internal team, we have Sometimes we have conflicting interests as faras like, how do we wanna build things? What text do we wanna use? You know, etcetera, etcetera. And so that's probably one of the biggest pain points is kind of managing that relationship between Guide C X and rave in Beyond That, Rails is just It's just this huge mammoth of abstraction and it's really spaghetti code, and it's really it's pretty gnarly. Um, so I'd say that's probably the main, the other main pain point. And then, besides that it's just kind of solidifying our processes Aan den as faras strategies. We use a lot of zoom calls. Um, we just talk. We talk about stuff all the time. Um, we just barely switched over to um or scrum oriented release schedule Dev Process saying on dso were kind of right in the middle of figuring out exactly what that process looks like, and we're writing it out. Every time we learn a new pain point. We're like, Okay, this one sucks. How do we fix it? And then we write that down. Kind of like our own agile manifesto kind of thing. Um, but yeah. So, like writing stuff out and kind of just solidifying process, codifying our processes as they come up is a big strategy that we use.

at least where where I am on don't know how many people are coming from University of Utah, but no in Utah, at least likely hydrate area note is really popular. Um, and so that's probably the main one. Noting JavaScript is kind of taking over the Web space we also use Docker was is another big one that we use and graphic ul ous faras communications. Slack is kind of the main thing, although at my job specifically, we're talking about dishing slack for discord because it's free. Andi just is good. So that's, you know, something that might be used a lot, um, software programs. We all use V s code for our editor. Um, we are we really, really like the extension platform that V s code offers really allows us to, like not just personalized the i d. But personalize it for our team. So, like you can have you can ship packages of extensions. And so when we hire someone new, we could say, Hey, here's this. Here's the extensions we use downloading right. And it's just like one link, which is super cool. Um, trying to think I mean, post grasses I pretty much exclusively worked in post Presas faras Data basing is concerned. Um, assed faras frameworks. Yeah, with on the note side expresses really popular. Happy is really popular. Um, sales is another, um, node framework on the back end. But really, I mean, express is pretty much it. Um yeah, as far as I mean and And this is, I think, something I want to talk about. A Sfar is like models and algorithms. One thing I think that I've missed out on not going through university is that I am not super versed in models and algorithms. So I don't think that we have any specific ones that we use for a sorting. I also don't know if our data is intense enough to reach for, like, pre build algorithms just because our product is pretty simple. Um, yeah. I'm trying to think I mean, like, again a lot of zoom. We use a lot of zoom right now. Um, it's pretty much yet