What's up everyone? I'm here live with one of our other participants, Jared Mcdonald here. Can you tell us a little bit about who you are university age major first off? Definitely for sure. So again, I'm Jared Mcdonald. I'm writing from Indiana University Purdue University Indianapolis or, luckily, IUPUI. I'm going into this is my senior year. And I'm an IT major and I think that's all yes. Yeah, yeah, absolutely. So your team, I believe, is called Nightwatch. Is that right? That's correct. So inspired by Bobby Knight. It's kind of what we're going to hear. I love it. It's a mental health dashboard for professionals to get a quick IoT enabled kind of high-level Excel spreadsheet in a way for you to get quick analytics on your players. Oh, that's fantastic. Are you just out of curiosity? Are you leveraging any of the industry partners here? Definitely. Biggest one we've been relying on here is IBM. Okay. So we've gone full serverless, full IBM cloud. So we're hosting in a object storage is where the front end is placed, using Kubernetes to manage our SQL server. And then we're also using their containerization platform for the Python Flash backend. That's awesome. Just out of curiosity, how's it been engaging with the IBM team here? Oh, they've been tremendous. So we've also been using Watson, which is one of their proprietary machine learning algorithms. And with Watson, we had a lot of hiccups along the way. It's a brand new technology for us. So it was very important that we kind of figure that out and they were able to help us get going. They showed us some examples and then they helped us debug a little bit too. Yeah, and that's what I love about kind of this conglomeration between students and participants like yourself as well as industry leaders. That real hands-on experience with some cutting-edge technology from some big names like IBM. Definitely. And it's been very cool to just have them, you know, right next to us. If we have a question, I got stuck on a Kubernetes configuration. And, you know, usually you're reading through the docs for 20, 30 minutes. Hey, I'm stuck on this. How can I, how can I get this fixed? Yeah, because to your point, I mean, this is a crash course. It's 48 hours. And last thing you're going to do is be scanning a code for 30 minutes for one semi colon or one, you know, hiccup that you may have not seen that they may see just do a quick glance too. Definitely. And that's been a huge thing as well. You know, we were up until 6 a.m. last night in the night before. And one of the big things we would do is I would just read line by line my code to one of my teammates and just talking through it. You really find a lot of those errors. But staying up that late, you run into a lot more bugs than you usually do. Yeah. How has this experience been for you? It's been really awesome. This is my first hackathon. Okay. So it's been really interesting. This is honestly, I spent most of my weekends by having the ability to do it in person with a team has been awesome. And when there's prizes on the line, too, it never hurts, right? Definitely. Now on a weekend, very exciting. So usually I'm writing a bunch of open source code where hopefully some developers see it. But now we get to write some open source code that hopefully we can win some prizes as well. Yeah, absolutely. So it sounds like keeping staying up late. Are you sleeping here, too? Or are you going off? Luckily, one of my teammates is actually a Butler students sleeping in the dorm. But it's not sponsored by Bang Energy. Bang Energy and Red Bull have been keeping us going. I can imagine. I remember those days, too. So how are you feeling? So I think the pencil's down code freeze was at 3 p.m. How are you guys feeling? Good. Is it working? Definitely. Yeah. We got about 95% rather than running. So our front end doesn't have quite the API back and we want, but pretty much otherwise our API is working great. Our SQL procedures are working and our flashback and is working great with Watson. So overall, I wish we could have had another 20, 30 minutes, but I think that's always going to be the case. Yeah, I mean, the fact that you were able to accomplish what you could in this short time frame and utilizing technology like IBM is no easy feat. We know how complicated that can be because it is such an industry leading technology. So kudos to you guys and kind of your team and honestly, I just hope the best for you guys. It sounds like you guys have a really cool technology and looking forward to hear from it here soon, brother. Gotcha. Awesome. Thank you. Appreciate for joining me and all the best of luck. Thank you. Have a good one. You too.