Welcome back everybody to uh another episode of Energy Bites. John Cowan here with uh my wonderful co-host Bobby Nean. What's up? How's it going Bobby? Great. Going great. We've got our guest today, Andrew Munoz, CTO at Forecast Now. Is that correct? Cool. Swiss Army knife of oil and gas. Yeah, thank you for bringing that up. [laughter] I'm jealous you stole that uh that tagline because that's I feel like I'm similar in a lot of senses that I looked at a lot of profiles. Yeah, because I was trying to figure out like, okay, I don't want to do something stupid like polymath or some dumb like that, but I'm like I'm doing geoysics and engineering and I've like picked up a lot of skills data science, but I wanted to have something that was sort of tasteful that was a good tagline kind of coming out of being an being a geo physicist and an operator. So, no, it's it's good. I like it. Thanks. Uh [laughter] before we get into it, if you're liking the podcast, please go give us a review. If you're listening, if you're watching, please hit the like button. Try and subscribe. Um, we're getting really good responses and feedback. We really appreciate uh you guys listening in. So, with that, get that out of the way. Let's jump into it. Tell us a little about yourself. So, yeah. So, I I've spent um over a decade working for for operators. Um first at at Newfield, I was a Jew physicist and uh you know, had a lot of great experiences, great mentors there. Um and uh and then I hopped over to private equity uh uh operator inside natural resources. We bought pioneers position in the Eagleford and um got to be the geo physicist for that that company and and build a lot of my own tools and um built a lot of the workloads doing things the way that you know I wanted to do it on the geohysics side and met a lot of great people and uh and now I um sort of jumped into the the sharky waters of entrepreneurship and joined uh uh you know forecast and uh I'm the developer for the software now and have kind of rewritten it in the way that that I felt is a really optimal way of doing it. And it's it's been a great ride so far and I've got a lot of lot of history we can dive into why you know why I've done certain things and where I've acquired certain skills. Um so whatever you guys want to talk about I'm open to. Cool. Yeah. Um want no I mean I guess just as far as you know I guess maybe coming when is the first time you touched you know coding or tech or when did you really get that bug? Yeah. Can you to that point preface that with just give the non uh oil and gas folks just a a brief understanding of what geoysics is and what it is what they what you guys do. Yeah, absolutely. Well, first I'll uh go ahead and plug uh the energy 101 podcast. Uh you can hop on that and get a really uh highle overview of uh geoysics and geology and how we're important in the industry. But basically geohysicists are responsible for interpreting um this data that creates an image of the subsurface, creates an image of where rocks are deep down and it's called seismic data. And we use sound waves to build those images and we interpret them and then use them to plan and develop oil and gas wells. And so you can't see thousands of feet into the ground. So this is a way of of remotely doing that. And that's the primary skill that geo physicists uh bring to uh oil and gas operators. And we're needed to derisk wells to plan them to um figure out where oil and gas is in some cases. So for conventional um conventional wells, we really are identifying where it exists. Yeah. You're kind of the explorers so to speak of the the subst. That's why I loved it because it's like when I first saw it, it's like, oh, you're like building a treasure map, you know? You're the you're the treasure find. You're the explorer, right? This is uncharted territory. And so what you're seeing is things that humans have never laid eye on eyes on, but you're you're seeing it remotely. And you're like, "All right, let's go. Let's go find this. Let's go explore." And it happened over millions of years. Happened over millions of years. All kinds of crazy features to it and all that fun stuff. It's incredible what the Earth can do over millions of years with burying sediment and eroding sediment and and shifting it and Yeah. And causing causing breaks and faults in the ground. And it's it's a pretty neat world. And not only the time scales, but the the uh size of these basins is hundreds of miles. I mean, these basins are huge. And the size of these geological features are are huge. Um so we work in very different scales than what most people live in. Yeah. But even with that, it's I mean it's not all, you know, homogeneous either, right? I mean, it's like for one, you know, within within a few miles. And I know I spent some time working in the Eagle for too. It's like you can go a couple miles up, down, dip, whatever, and things are totally different. Like very different. Yeah. And it's like, yeah, you could put wells and and a lot of the lot of this area and unconventionals, but it's not always economic. It's not always a product that you want. You know, it's uh definitely times for oil and gas and and so knowing where you are and understanding how to economically extract uh these minerals is is really important. So, how did you get get into kind of coding and the tech side of things? Yeah, so that that's an interesting story. I I never was a software engineer like that. I don't have that formal background. I started early in my undergraduate with some undergraduate research projects uh in forran 4ran 77 specifically and I was doing some uh reduction to the pole magnetic filters. So like a magnetic based geoysics and just really simple projects like doing 2D for transforms and kind of programming them and doing some neat uh some neat research projects. And then I got a little more advanced. I I started working with a professor in my undergraduate um where Robert Vice where we were doing uh tsunami modeling. So we're doing threedimensional uh smooth particle hydrodnamics and we were doing C++ using C++ to to build these um threedimensional tsunami models and it was really cool and measuring inundation lengths and um I learned a lot about GPUs in that time because SBH uses uh GPUs to do the computations. So I I got a really early introduction to Nvidia Tesla. Yeah, really early. this like 2008 I guess 2009. Yeah. So pretty before Nvidia kind of blew up in the AI tech space. Um, and before, you know, people really had a lot of GPU programming, we were programming in CUDA. And CUDA is like a very low-level language compared to, you know, what exists now for GPU programming. And it was a great introduction to to that world and to the hardware and the software world. And then I went and visited um Crowd School of Minds for graduate school. And I this is a very um something I can highly recommend. If you're under undergraduate and you really wanted to get in a certain graduate program, buy a call them and and schedule a time, buy a ticket, plane ticket, go there, tour the campus, meet the adviser, and spend time learning about them and and seeing why you might be interested in working with them because god that was such a good such a great way to not only get into a competitive program, but to just get to know it and to understand it. So Dave Hail was my adviser there. just absolutely brilliant guy, right? I mean, just just a workhorse and knows so much um you know, he's instrumental in building landmarks um uh software systems for geohysics and just like I think he I think he actually I don't know this is how true this is I think he took the original like C code and and and turned it all into C++ like turn all into object-oriented code for the whole decision place platform um would it exist today? So don't, you know, landmark folks don't don't come after me, but I pretty sure he was very instrumental in that and just a super sharp guy. So pretty good person to be uh learning from. Yeah, he's a great person to learn from and he's he's very involved in what you're doing. So he's like really in it every day with you and he's trying to do things himself. Like he's very he was a very prolific researcher. He retired not not long after I left, but um he's a very prolific researcher and a really sharp guy. So what was cool about him was his involvement and teaching you and and having you kind of throwing you in the deep end learning. Yeah. Um and from him I learned um Python and Java. So he was a big Jython guy. I don't know if people know what Jython is, but dive into it. That's what Yeah, that's what we're here for. Prior to Python 3 version 3.0, which is what most people use nowadays, Python 2.7 um could integrate with Java using these Jython libraries. And so you can basically take a statically typed language that compiles like Java, which is really fast. I mean, when you're working with big data sets, seismic, you need something like that. I mean, you need something that can run really quickly. And this is before Python really had a lot of the vectorzed optimizations that it has today. Um, so in Jyon, you have all these compiled Java classes that you can, you know, work on and create and and so he had this great library called the Minds GTK, which I think some are still maintained by some ex- studentents today. um that has all these fantastic Java classes for working with seismic data and and and log data. And so I I did some research based on that and I started a master's degree and I decided to flip it and do a PhD and then it just you know it wasn't really for me I think and I I was happy to hop out of that and go work at Newfield in Denver and and fortunately I timed it in 2014 to where I was getting right in the crash. [laughter] Yeah, got the job. That's when I got into the uh industry as well as July 2014. Exactly. Got out, got got my full-time job secured. Um, and sort of rode that wave. Um, but I learned so much there and that's where I got the base for my my Python uh programming skills that I use mostly today. And I still do a little bit of um Java if I ever have to do any type of work with Seismic and and Jython specifically. still have some builds that that let me use some of that code. But um but I throughout my career in Newfield, I did a lot of geohysical work using some some of those mines GTK libraries and code using Jython [clears throat] and I got more and more proficient in Python as it went along too. And I think the real breaking point was I was making all kinds of little libraries for doing log analysis, rock physics, um you know, programming things that that you just didn't see in these mainstream geoscience packages, you know, looking at log data and doing petroysical analysis. And I was getting more and more proficient. And then the break point was when I I moved down to Houston and I was on exploration team and I was sort of helping the assets at the time optimize their developments and and I was doing some work with geohysics, a little bit of work in data science myself and then this they hired this guy M. Burton who was a uh reservoir engineer coming from Inodarco and he was on their data analytics team and they're sort of like known around the industry. talking about a really good program, really good data analytics team and data analytics team and they had they used agile uh methods for development and um and he he came in and create started this group with Sebastian Martran who's at Hess now he they they had this this group they formed this group where they were trying to do data science and analytics you know inside inside Newfield and um use this agile you know methodology for development and so I didn't actually like join the team but I was the geoscience member of that team. So I, you know, started kind of early on with them bringing in geoscience data and and my boss was really happy to see that, you know, he wanted us involved in that. What what another novel idea bringing inmemes to the to the data science groups instead of just passing it off to them. And that was me like I was more focused on like okay, I knew a lot about exploration. I knew a lot about the data because I was trying to do things with the data. And so at that point I didn't have any SQL experience. I didn't really know a I knew a little bit about databases but um I was sort of involved in some of the data science projects because I was helping bring the geoscience data in so when we were using external uh vendors and things like that. So we get this group started and Matt brings all these great ideas around um you know linear predictions and multivariate linear models and statistics and you know like really basic stuff you got to get people over in order for them to to do to understand and accept data science, right? And so um we spent a lot of time educating and creating really simple ideas and that's where I really started to expand my Spotfire skills. I'd been using Spotfire for a lot of other things. Sure. Um but on from the data science perspective, I really started expanding my Spotfire skills programming in R programming in Python in Spotfire before like it was um before it was really easy to do. Yeah, the Python data [laughter] functions like right way easier. Yeah. right when Spotfire X came out. Uh Spotfire uh skip from 7 to 10 like Yeah, exactly. Skip from 7 to 10. Um and they were like it's X and so right when that came out then you can use Python data functions with a lot of headache uh to to get it working. And so I started using that a little bit more but we were more R focused at the time. And so um did a lot of great stuff with them and I I started learning a little bit of SQL a little bit of database and and I just learned the workflow of how to do you know production prediction and how to integrate all this data, right? And then when um Encana announced the acquisition of Newfield, I was like, "Oh, this is this is fun." So I had I had gone out and I'd looked for um I had gotten a job with um Insign and so they were in the middle of closing this deal with Pioneer buying the Eagleford asset and they wanted me to be the geoysicist for that and like all right we want you to come in and stand up the geohysics program and we we had to buy a lot of seismic we needed to buy like a thousand squares of seismic which is a pretty big area. I mean that's you across a few hundred miles. Yeah. And um we needed to buy a lot of seismic and um understand this very structurally complex part of the ecoorder. And so I was like all right well I would also like to do all this really cool data science stuff. I've been working on this for years. You know I've got this programming skills like yeah that's great. Let's uh hold your horses. My boss Jennifer was like just make sure you get the geoysics done and then we'll talk about that. I was like all right. So I get so I start the job in like May of 2017 and I um or was it 2017? Yeah, it was 2017. Um, I uh immediately start um man, no, was it 2019? Shoot, I don't remember. Sorry, guys. Whenever I started insign Whatever year it was, it's just pre pre-COVID and post really what what I can't remember if I think my Yeah, my first child was already born. So, it was definitely after 2017. Um, so I guess it was 2019. So, 2019 I start and we um and I was so excited to get through all the geohysics part. I mean we needed to have it done like it was really important like it was very integral to our s to our success in operating. Um I spent a week over that thousand squares just interpreting all the data like I finished it like I picked like 700 faults. I picked four different horizons like picked the beauty the eagle furford the anekacho the Austin chalk and I was done within like a week and I spent like 14 hours a day doing this because I wanted to get it done and they're like you didn't have to do it that fast. [laughter] Like no I've got motivation. Yeah. I want to do this and so and then we went through a couple things like okay I went I conditioned the data did some gather work and things like that and then I you know adjusted it but I was done really early so by the fall I was and we were starting to operate our first rig by the fall I was ready to start doing my data science work all right so I started from the ground up and I built everything kind of in spotfire with Python and R scripts and started building all these dashboards and the cool thing about Insign was we had all these fantastic uh techs and uh people who knew programming and um who were just instrumental in creating these amazing backend that you know we could plug into and it allowed us to do you know these really cool analytics projects. And so I got to work with these guys and I got really proficient at SQL you know learning it from them and just practicing it. And then I was able to start building my own um you know tables and databases and I started just I created this whole you know data science uh these all these data science products that we're then using to help inform some of our decision-m. Yeah. And I was integrating the geoysics data, the attribute data, um, geologic data. And so I just got a really strong, you know, background in doing that and building from the ground up and it was a lot of fun. Um, so from that I I we you know decided to sell the company and uh put it put it up to market and had a you know great successful exit to Marathon. And then once uh our TSA was up with that in March, I uh I had I had already been advising Zack Copan on on uh on forecast and I was like he was like, "All right, well, let's let's do this. You know, you want to be the developer this." I was like, "Sure, sounds fun." You know, it's entrepreneurial. I've always wanted to do that. Yeah. Um and get a taste for that. And so, from the beginning, I just just helped sort of reboot. You know, he had a great minimum viable product. He had a lot of uh great customers that were using it. And I was like, "All right, let's start. I'm going to build this how I the same vision, right? How I want to do this." And so I built the whole back end and then we went through and um you know, rewrote all the code for um for the software. So and then released it and have been been selling it since. So it's it's pretty fun. I honestly think that's probably one big reason for Y's success so uh quickly is just you know having a having the subject matter expert or the user help write the software that they are using. Exactly. Is a very critical uh component of software development. I think that's where a lot of people stumble. Right. is you go hire a dev shop or you got this big dev team and then none of them have any or they have very minimal understanding of what the actual workflows are what the realistic you know whether it's the databases or the security the permissions or where the the structure of the all of those things they don't ne you know they think of things in a per like in physics right it's in a vacuum right and so everything happens perfectly in this vacuum but in the real world that's not how it actually happens right exactly [snorts] that's that's that's really How did uh so your like programming journey so to speak was that pretty much all selftaught did you get any kind of formalized training in that yeah kind of sense or I didn't you know I had I had a few mentors you know I had a few people that I could kind of tap into but to be honest in the oil and gas industry there's not that many um you know I I had spent some early time um looking at a lot of stuff that like Matt Hall was doing when he had agile geocciences he was always producing some great content and it gave me a lot of you know good ideas of how to leverage Python and my own workflows. Um, but yeah, it was honestly a lot of it is going out and finding a problem and then just figuring out a way to solve it, right? It's like, well, I've got this toolbox. I've got this giant toolbox of of of Python. And at the time, I was using a lot of Python, too, but really started moving more towards, you know, later stage Python. And I was like, I can do a lot with this. So, I started finding all these problems and trying to see if I could solve them using programming. And I just had to learn how to do it. You know, over time, I got more proficient and found more advanced tools that would help me along the way. And that's how I ended up, you know, where I am is just trying to solve every problem I found. Yeah. Yeah. I can't agree more. I mean, yeah, you can do whatever formalized training you want, but it's never never going to be tailored to what you're trying to do. And like, you just have to I tell people all the time, you have to find a problem and try to solve it. And it may take you longer than it would take you to do an Excel, but like I promise you, it's worth it if if you like figure out how to do it in I like reading. Like I like editing and reading technical papers. I do it, you know, a lot for SUG and things like that, but when it comes to reading about programming, it's so boring. It's so bad. It's just terrible. I just so much rather do it and keep failing until I figure it out and and then I go research it, then I go read about it. But like, it's got to be practical for me. Yeah. And I think like to your point though too, having good mentors helps, too. Like someone that can unlock it. I mean, I I'd say I had a couple at Kico even where like, you know, I'm starting to learn R. I'm like, I know how to do this in Spotfire. How can I do it here? and like someone unlocks something for you and then it's like boom, you're off to the races. Exactly. And and those things exist, but there's also a really important component that a lot of people miss is like there's so many ways to learn about how to do something or how to understand a package, you know, in our in R, Python. But the really challenging thing is how do you understand how a process works from its fundamentals? And that's where the mentors come in a lot is like they might not know programming language. They they might be new to them, you know, they're really experienced, they've used software, but they know how that software works. And so they're the ones you can go to to understand the fundamentals and how to actually build something from the beginning. And so that's what I can say my my mentors did the most is like helping me understand how this is working. And so then I can like okay now that I understand this I can apply these tools and figure out how to make it work the same way. It's I mean it's especially important when you're making that jump from like you know I'm just messing around with my you know uh fantasy football data dashboard that I'm building internally versus spinning up a talk about that too if you want problems and yeah but even that but even just like I mean writing scripts and stuff that people are going to end up making million dollar decisions on like like the the stakes are so much higher much higher security there's so much more that goes into it right like to your point understanding ing how it actually works at the core because then you start getting it especially with the type of the amount of data that you guys are talking about. You have to optimize. So it's like okay it works but now it take you know it takes 30 seconds to load the page. All right now we got to figure out that problem right. Well when you have customers it's like oh my gosh like [laughter] every little thing is fast is yeah is really important and and if you you present a fast product you can never slow it down. It's got to go only it's only got to go faster. [laughter] So that gets even more challenging. on and you know three to five seconds staring at a website is so much longer than you really think it is if you're a user and it just that's how long it takes to load pages. But to that end you have to have that step in between to make it work well before we make it work [laughter] fast because like a Lamborghini with bad brakes is you know really dangerous too. Yeah, that's why we're talking about like is is there a point where we get off like right now you know our front end is built off spotfire and we can do a lot with that. I mean, it's very powerful and we can make modifications really quickly and do a lot with it. Um, and we're so customized with it that it's almost like having, you know, it's almost like having custom software. So, I think the thing that the only way to get faster is to, you know, write your own React frameworks, right? Like you have to have your own framework and be able to control how things are cached in order to make it really fast and really interactive for the users. And that's kind of our next step. It's like, well, that's really the only way we can go. Make it quicker. Yeah. Yeah. buddy buddy of mine and I want to get him on here eventually. He keeps putting it off but like he wrote a production optimization software um but he was probably started out with a lot of Spotfire. He's really good with it but he had worked with this Ukrainian developer and like they wrote their own visualization library in React like not even using like you know plotly or any of these other things like they built their own to-do because they knew what they had to do and it had to be fast. That's how I would do it. And I mean, and that's how we're going to do it. And that's, you know, you've got the perfect wireframe with Spotfire because it's got all these Yeah. It's an interactive wireframe. I think I was telling Zach that before. I was like, dude, you've got what you need. Like, you hand it to the right developer and they can run with it. Like that. That's the part of the hardest parts is if you don't have something explaining an interactive wireframe. This is a functional thing. Like, let's [laughter] rebuild this better. you know like how do you like yeah you have to explain to react developer how do I lay out all these states and how do I make these thing these plots that interact and how do I make these you know different different hooks and like you have to you have to know they can look at the tool itself and reverse engineer it essentially so it's like with a good a good developer like that so yeah exactly like this is the perfect way to start out yeah no that's I mean that's a direct camera uh [laughter] moment but that it's a really is just like a pro tip for anybody in that very early stage page MVP software development stuff is like if you have you know a free or white label type solution that you can uh leverage out of the gate. It helps so much down the line because it one it gets you started and moving which is the hardest part of any business is doing it and you can make money on this as it stands. you can start bringing revenue in and probably if you're software it's ARR which is a nice fat multiple on top of that but then it's also very easy to just say here Mr. developer make this right like you don't have to go and wireframe every single step yourself from scratch like even me like doing some BI development stuff if someone can give me an Excel sheet that's functioning like this is the logic that I want to build or even just can draw it on the board like but half time people come like hey I want you to build me this like okay what does that mean I mean like I'm a visual like show me and I can make anything happen but like exactly or I mean you also this happens all the time still uh in my experience but it's like hey I want a button that does, you know, you put your your uh requests in with features and you put as much detail into it as possible. The dev developer goes and they, you know, they check it off their list, but then you go and you actually use it, you're like, "This isn't what I want." You know, yes, there is this feature, but it's unintuitive. It's not where it needs to be, whatever it may be. And so, just having something simple like that where it's like, "Hey, look, this is exactly how I want it to work." Yep. Streamlines everything. And you get to focus on what you're good at, which is usually what you're selling the product to to do, right? So it's like, okay, you know, I know oil and gas and and how I want, you know, these tools to work. So that's what I want to focus on, right? I'm not a front-end developer, you know? That's that's something I'm having to learn. I always really wasn't even a back-end developer. Like I had a lot of Linux experience. And that was again another thing that I learned early on was like, okay, when you're in academia, you have to learn how to build your own, you know, backend and your own environment. And um and so fortunately, I had that. And so when I had to stand up my own server, I was like, "Oh, this is this is complicated." Like I thought I could do it really easily. Um, and you know, I can navigate Linux really well, but man, there's so many things to consider and there's so much security implications and and administrative things that you have to do and that takes a lot of time. Uh, but you know, it's fun learning new things. So, I enjoy it. And when it's a motivated, a you're motivated because it's a business that you're part of and you have obviously the equity in it, but just you know, when you're motiv motivated by those problems like Yeah. I was talking to um Sean, if for those of you who don't know, one of uh Andrew's former colleagues is now my colleague. Yeah. Sean has one. So yeah, we're uh we were talking shop, but he's like I I can do a little bit of networking, but I hate it. You know, like I could never like that could never be my job, but like you know, like but there's certain things that are motivating to you and then we can lean into those and it's fun. I hate to bring this up on the podcast. I hope you don't get mad. Sean, have you seen his YouTube shorts and YouTube channel? I looked at a couple but Okay. He's got some funny ones. I thought it was I thought it was cool. I was like, "Oh, this is awesome." like he's got some really really funny content on here and it's like sort of making fun of you know junior versus senior software developers and things like that. But yeah, that's an example of a really sharp guy who helped me along and helped our journey along and ensign you know who's just instrumental in creating these tools and the back end. So like with that I mean say what you're using now say at at forecast like what are some things that you can point to like oh that was an ensign thing that I brought with me or that was something I learned at Newfield or different stuff along the way and like how's that kind of culminated in what you're doing now? It all is. I mean, especially in the production kind of data space, right? Because everyone every oil and gas company listening to this has production data, right? Like Yeah. Exactly. Yeah. I mean, most of it is just like the the knowledge of how to deal with reservoir data, reservoir engineering data, like production data. Yeah. Um what is important when you're looking at analytics, uh when you're looking at wellheader data, so you're looking at job size and spacing and how do you classify things and what importance do you put on that when you put it in your front end? like how do you how do you emphasize certain things? What type of plots are important? Do you want plots? Do you want rate plots? Like having all that knowledge is super important for deciding what's what's important to show people. Yeah. Um because if it's not important, they don't want to see it. They don't want a million options, a million buttons. We try to keep it as simple as we can because like well, we just want to show you what's important. What you really need to do to get a value on the steel or a value on your wells or what you need to do to do a type curve, right? I just want simple things, simple intuitive things. Yeah. If I can have a land I mean this is this is what's amazing about the way that we we built forecasts. We have landmen picking up the software who don't have very smart but they don't have technical backgrounds and they can go and run a deal. You know they can do for they can do forecasts and they can even adjust them and and kind of make things fit better and they can put on all the parameters and and all the inputs that they need and they can run a deal in in no time. And uh that's the type of you know software that I like to build stuff that anybody can use. Sure. It's typically the best software is the best [laughter] software. Yeah. Yeah. When you can teach a non-technical person, you don't even have to teach them, right? You don't have to teach them. I mean, there [clears throat] was there was a one of our clients who's incredible. He's he's just super sharp. He's a he's a kind of a land finance guy. We we gave him a license at the beginning of Tech this year and like it was like a Monday or something. Just send him a send him a login. He was going to be web player, so it was really easy. We just send him send him a login and send him a link. And by the end of the week, I mean, he was like a power user. I mean, he was asking me questions on like the third day of Vert. I was like, "How? Wait, you've only been using the software for like two days and we've been at a conference here in Denver. Like you're still using it and like really good with it, really proficient with it. And so it it's amazing how fast, you know, some people can pick it up and run with it. That's a testament to to y'all. Not necessarily. I mean, obviously I hope so. Yeah, [laughter] that's No, I mean that's that's in my opinion UI UX is one of the most challenging things specifically in our industry because we have gotten so used to the like old school hey it's not broken don't we're not going to fix it we'll add new things to it but we're still going to run on this old you know uh antiquated system right on a virtual machine that's run on Windows 95 and like very archaic type stuff I think but also to your point though too is like knowing what's important because you know you can fall into a trap of and I think some companies chases of the customers always write oh yeah we'll add that feature and then you just it's just bloated with buttons and pages and stuff and no one knows what the hell to do. Yeah. You know where it's like no we know what 80% of our people want to do with this. We're going to focus on that core functionality. Yeah. I have a rule and I tell clients this too. I'm like if I have two clients to like two paying clients ask me for a feature [clears throat] I'll usually have the next day. like I'll I'll just throw it in and throw it throw it out to them like because that's like if it's that important that two independent people who don't know each other asking me about it then it's important enough to put in the software and then if there's like at least I it's kind of rough but if there's five people who ask me for a specific feature not clients that's usually when I'll also do it got and just throw it in the software you know if I have to you know run it overnight I will for something simple right like a button or like you'd be surprised what's simple some things are simple some things are really something that sound simple are really complicated yeah simple but not easy yeah Yeah, like I'm working right now on this way to normalize all the formations uh automatically because people take that for granted when you have really cleaned up data sets from from from IHS or from Paris. They do a really good job of going through and and picking out these formations and cleaning them up and looking at target zones and all that. And so our our intern buddy like he has no oil and gas experience. He's a financial like financial economics but he has programming Python experience and he tackled it great. And I mean we showed that at Energy Tech night uh how we had kind of cleaned up the Anodarco basin and it's all automatic. It's all fuzzy logic and you just sort of trust that the operators got you know some exposure to what it is and there's there's rules around it and I'm applying like some geological things like okay the Marramac doesn't go beyond this area. This is all Mississippi lime. Simple things like that um to to it. And then that pushes us into our spacing calculator. So now we're going to roll out this, you know, massive tool that does really accurate spacing calculations and incorporates parent child and code development and threaded wells and like all these classifications that let you filter them down really fast. And that's integral for doing fast type groups because you want to pick out similar wells to the type of development that you're going to do. So I'm not going to pass this opportunity up to promote the hashtag hamadaro. Oh, [laughter] yeah. That was that was a funny evolution. So, we were Zach loves like Oklahoma, right? Like he's he's in Oklahoma. He's he's he's Oklahoma born and bred. So, he's very like, you know, involved. You find that pretty often. They may be more proud than Texans. It's pretty It's pretty accurate. Yeah. [laughter] But it's great. And we get a lot of great, you know, local uh content and ideas from that. and he's he's like very pro this idea that Harold Ham just wants to acquire everybody in the in darker basin. And so like yeah that's that's awesome. He's and so we were talking about ideas for Energy Tech 9 and how we could do a demo and I mean the software is is I mean it's super fast like we can literally do an evaluation and come up with a number of what the PDP value is of the entire Anodarker basin in a few minutes. Like it's it's that fast. And we did it so fast we put it in a video for energy tech night for the for the demo. And so the idea around that like what if we just consolidated the major players in the Inodarco to continental? What would it look like? Right? So that's where Hamadarco came from, you know, Harold Ham Hamadaro. Um and so yeah, so we're we're we're promoting that. I think Zach even trademarked it. So like we've got [laughter] we're all about it and the Continental engineers love it and have a great time with it. And again, it's a it's a fun concept to kind of play around with. Um yeah, it's a you know, it's a very real possibility. kind of has no rigs running in in the Inodarco and people are kind of focusing on the Perian and and and doing other things and Ham's like what are you guys doing? This is crazy. This is a premier oil and gas basin in the United States. Put money into here. Focus on this basin. And so he's like if you want I will you know. No, it is crazy. I mean because I mean and obviously I think someone from uh forget what but they showed the graph and it is amazing how much the perian's contributing right now. Yeah. But like there's I think the value is in some of these other basins. I mean, we've been lucky at GME. We've got two deals so far where like getting him at a apparently a pretty good discount. You know, time will tell, but like seems to be going pretty well for us so far. And there's running room all over the place. I mean, I some people might disagree, but I mean I you know, I think that as oil price sustains and stays high, all these secondary targets are going to be economic across the US. And as we go back and and learn more about them and um we apply some of these more modern frack techniques that we've been doing and I know fracks Frank design has been kind of similar over time, but I mean we're running casing for cheaper. You know, the tools are better, we're more consistent. Um, you know, I think we're kind of settling on a 3,000 lbs per foot design across the US that seems to be pretty standard. Um, you know, a kind of a cluster spacing that's pretty standard. So, I mean, we're getting better and and better. I was going to say there's so much there's so much opportunity in the OG shale basins to come back in cuz I mean, yeah, I've only we did it. We wrecked a number of wells at Insign and they're great wells. That's the thing is like just thinking about I mean the first five years of my career I was a frack engineer and uh thinking about the fracks that we did in 2010 versus you're telling me that 800 lb cross link fracks aren't the best type of frack? The amount of cross link fracks [laughter] I have pumped is just ridiculous. And I mostly worked in gas bases just to give you an idea of how horrible those designs were. But uh no, it's it's yeah, there's I think there's huge I that's one of the biggest things I feel like I've learned in my experience in this industry is the sexy thing is not where most people make most of the money, right? It's the definitely not, oh well, here's this thing that's been here for a while. It's actually proven. There's lots of data on it, but it's not the new like even just conventionals, right? Like conventional stripper wells. You know how much money individuals make on convention? There's tons of bypass stripper wells, right? Yeah. Like coming in. My father-in-law has some stripper wells up in Louisiana and he can come in and shoot a 10 foot PF or 10 foot zone and double the production overnight. One wire line. Is that worth it? Absolutely. Yeah. It's it's uh it's crazy. And so I think yeah that's just a big thing a lot of people don't pay attention to is that like hey these are the oil is not going anywhere the gas isn't going anywhere just because it's not the sexy thing that the investors want to hear doesn't mean that there's not value to it. Absolutely. Yeah. One thing I mean you know one of our main deals here is that we want people to take maybe new ways of thinking or doing things. Um, so you know, speak as much as you want about it, but like how are you guys deploying Spotfire for forecast because like I mean pretty much anyone I know in oil and gas is probably deploying it on prem and they're on a Windows box using SQL Server, you know, as the database behind it and everything. I mean like um yeah, how are you guys deploying it? I mean I can't ride that too much for an operator because we did that. We did that in No, no, we did too. I mean I'm not knocking but I mean I think it's people realize they can do it cheaper. Yeah, I think you can do it significantly cheaper even not having to host it yourself. [clears throat] So that's that's kind of what we do. So what what areas do you see like room for improvement or have you seen kind of gains or optimization on on your end? Yeah, I mean I think people should be using the web player more. I think that's going to get more and more popular and even for for people who are using it from from an analytics license or business author perspective where they're editing it and creating things. Um, the web player is getting more and more powerful and Spotfire is deploying tools that help you autoscale and help you use uh containerization to to deal with the complicated mess that they created in some ways on the server side for for deploying a web player. Um, because you got to use Python nodes and R nodes and you got to use a server node and you got to make sure that they're not on the same machine or like they're at least containerized so that they're not conflicting with each other and stealing resources. Um, but it's so powerful and it's so fast because we host the data on the same bare metal servers. Like we just we host our own bare metal servers and I just, you know, I just lock them down and and you can have the spotfire creat I mean I want to clarify that too because like because some people like bare metal maybe like they actually have their own server Mr. Hughes. Yeah. Yeah. Yeah. When I say bare metal server, I mean it's through a third party contractor like they they stood them up and I just said, "Hey, I want that machine and I pay them a monthly fee for it." Yeah. And um and so coll-located. Yeah, it's it's like colloccated, but we didn't put our own hardware in there. I mean, they own the hardware. If it fails, it's on them. They'll give us new hardware. Sure. And I just use like a backup service that, you know, I can just replicate it, you know, the next day if I need to. Um and so we've got um our own bare metal servers and then we're expanding to this bare metal cloud idea where they basically keep their own servers running and then partition them to to people who want to just turn on a machine um on the fly. And so you can use tools like rancher that will you know autoscale kubernetes and and um which you know controls docker images. So it's like you got all these layers of autoscaling that you can use to um horizontally scale your your web players. And I think that's where most people can and should go with spotfire because typical cloud is like okay it's cool but it's just so expensive and so limited. Shock shocking. Yeah. Right. And so I can do so much with um you know with with Python and R scripts and and like a web player that it would amaze you. I mean there's I started writing script. One of the things that um you know not a lot lot of people think of actually write scripts that that write out my axes because the axes and the spot fire plots can get super complicated especially when you have a lot of options a lot and you want to keep it simple and you know we're on like a consumer license for a client so it's like they can't change any of that. Yeah. So you have to make it accessible in some really, you know, friendly way. And so I it was getting some of the things were getting so complicated that I just started writing Python scripts to write the to write the axis labels. And so it works really well. And so you basically just drop out a string and it'll like, oh yeah, this is this like, you know, 20 line long uh uh option full of options and ideas. And then of course you can iterate over things and make it easier. So yeah, but again, you know, I think big thing there too is like you're hosting on Linux because again that wasn't ever an option before. So I mean Linux is a free operating system. And then are you using Postgress as the database instead of I'm using MySQL. I'm using Okay. So you can use MySQL as the back end. Oh. Oh no. For Spotfire, I'm using Postgress. Yeah. Post 14. Spot as far as the Spotfire data. Yeah. So I'm using Postgress 14 for Spotfire and for spatial objects. So like shape files and things like that. It's just easier to handle them. And and that's free. And then like you said, I'm using Ubuntu 22.04. That's free. Yeah. Um, and Spotfire server tip, there's not a lot of great support for it. So, if you're struggling, just give me a call if you have a question. Um, Spotfire, I hope you're listening because I love Spotfire itself. Yeah. Typco, excuse me. But Spotfire is great as a visualization tool, but you guys are so proud of it. [laughter] Yeah. Yeah. And, you know, one of the problems is the community support goes all the way back to like version seven and and and even earlier to version five. And so it gets really confusing about what's relative, what's valid and what's not. So [clears throat] the support's a little rough, but um but yeah, I mean it can be done. We run ours on Linux and it runs it runs great. You know, we run our database on MySQL and and that connects perfectly to it and and and you can set everything up just the same way you would on Windows and you save a boatload of money doing that. So, I want to ask, how do y'all because this is something I never would have even thought about until Bobby and I worked together at at RDS, but how do y'all manage or what are some, you know, creative unique ways that you manage visualizing a bunch of data, right? Like when we were at RDS, right, we're getting 1 second data and the engineers swear they need to every single day even though it wasn't changing over the course of an hour by hour on a defit that's changing 0.02 PSI in, you know, a week. Yeah. Uh [laughter] you don't need every data point, but like let's talk about that because I do feel like that's something that a lot of people don't talk about until they get into it and they're like, well [ __ ] what do I do here? Yeah. I mean, I think the first thing is is is because like I told you before, like I'm building this and and with the perspective that I want for me like I want I I understand how you know companies create value and and I solicit a lot of you know ideas and advice from other people but but I know what I need to see and so one thing you can limit a lot of columns just just knowing that right like I don't need all this ancillary data that's being reported publicly like I this no one's going to ask me for this so so I can cut out data that way and kind of streamline it. Um, the second thing is I use a lot of the built-in tools in Spotfire for on demand data loading and I think it's it's underutilized. Um, they have a lot of advanced caching that they do that's hidden and so you can load stuff on demand uh really quickly that is on a database so I could bring in, you know, a bunch of wells. So that's kind of how a data loading page works. You bring in an entire state or multi-states or multi-bas wells. You just rope rope what you want and you can do some filtering down if you don't want that much data. I estimate how much data is going to be downloaded and then you hit set up project and then it brings in all the production data. brings in all the header data, all the forecasts uh that are like pre-done so you can have a starting point and you can edit them and and manipulate them in the software and you get all that data all at once and so I think that on demand component is kind of how you solve that because yeah it's hard to to cache you know all this data at once you know like like you know Brian Macau and his his sabata stuff like you can easily say well this is the database it's not going to change like everyone's going to look at Texas and this is Texas right so he can use automation and and throw that data in there and keep it updated. We can't really do that because everyone's looking at something different. We got people looking at Colorado. We have people looking at North Dakota. We have people looking at Texas. And so we need they need to be able to, you know, pull that data on demand whenever they want. Yeah. No, that's uh Yeah. It's like I said, it's just one of those things that like you don't think about until you're standing there and you're like, man, there's only so many literal pixels on this on this screen and there's only so many points I can put in those pixels. Exactly. Yeah. You do get limited. I mean, Spotfire, like once you hit, you know, a couple million rows, it kind of gets a little it gets a little hairy. It gets a little boggy on the on the map chart, but it's still one of the better like fastest visualization tools that's that's out there. It does. Yeah, it you can't argue with it. It It works. It works really well. It's super easy to use. Um it's it's fairly easy to modify and it's just so customizable that you can just do so much with it. You know, I mean, the text area is just literally a blank canvas. I mean, like it's a website. Yeah. can inject almost anything you want in terms of HTML and CSS into that. Yeah. So, super super powerful. Um, one I've been want to ask and it would be a great uh LinkedIn engagement question is R or Python. Oh, definitely Python. Yeah. Um, I will say R has if you're using Spotfire, R has the advantage of having very little overhead because the data types the exact data types that are native to Spotfire tear and everything. So, yeah. So you don't have to worry about like that overhead. So when you're talking about like interactive scripts and things like that, our definitely is a little bit faster um when it comes to like manipulating stuff in Spotfire. But as soon as we're out of Spotfire, we're going to be all Python and JavaScript because it's just like the Python just has so many powerful vectorzed functions and it's so easy to use and it's constantly evolving and um yeah, definitely Python. Sorry. Sorry our users. No, I mean it makes sense that the Swiss Army knife of oil and gas would choose the Swiss Army knife of uh the programming languages. Yeah. [laughter] I like that actually. No, I mean it's it's to me it's using the right tool for the job, right? Like R is more statist like math focused and stat focused and if you have those or like matt you know mat lab is similar too, right? Like we use mat lab in college all the time. I've never used mat lab again, but there's still lots of people that use mat lab because mat lab is good for what it does. Absolutely. Yeah. I mean for me the better question because people assume yeah you put r versus python I mean python just so much. I mean I for me if you said r versus pandas like or like say the tidy versus versus pandas like as far as a syntax syntax I'll probably take r and that stuff personally. Well okay but but you don't have the numerical optimizations behind it that you do with pandas. Yeah. So with numpy being natively used behind pandas, there's so much vectorzation depends on the size of your data. Yeah. So for big data sets, I think that No, I wouldn't disagree. And I've moved I use so much more Python than R. It's it's it's fun to get back in R when I get a chance, but yeah. And Shiny's got some like great interactive tools for plotting and things like that. So if you are using that, I mean, you know, you can expand on it and make some great interactive tools with R. So it's got a lot Python, you got Streamlit, and you've got Yeah. I mean, Poly Dash and all that. So there's a lot more to do. And then like you're like, "Oh, well, I can use statistics and do things like that in R." Well, you got stats models is is brought natively into Python, so you can do all the same functionality that you have. Yeah. And the community, I mean, both communities are very good, but Python community is just insanely huge. It's just massive. Yeah. It's just massive. It's like it doesn't seem like it's ever going to That's probably a terrible thing to say out loud and put into the universe, but it just seems like it just like there's all there's multiple packages for damn near anything you're trying pretty much anything. Yeah. like and most of them have documentation and stuff. I mean, one of my buddies has been putting stuff out for the maritime industry. Like there's, you know, four different things I've learned about this week that are packages exclusively for maritime data. It's like I mean, I think there's there's lots of ways you can use Python that almost makes it look like no code. I mean, you can you can put in such such simple functions that that have I mean it might have a little bit of overhead, but you can put in some really simple things that are so abstract that can do a ton of different work. Yeah, I I've been messing around with some workflows in for us internally and I can use uh OpenAI's Whisper uh audio to text transcription with two lines of code. That's unreal. In in a Google Collab notebook and it run it'll run and transcribe an entire podcast by itself in a notebook in Google Collab that is running not on my machine at all. Cheers for Jupyter notebooks. Holy cow. like that's a you know if you want to learn Python learn it in notebooks because you know true it's a great I it's it's [clears throat] weird to call an IDE but it kind of is like an IDE right like you can type in it and it can and you can run it um I was actually speaking of IDs what I'm kind of curious what you guys use because I have a funny sort of evolution of my IDE journey yeah I mean I I use VS Code and I have for the last couple years yeah very opinionated on this topic because my first like real coding that like legitimate coding that I ever said was when Bobby showed me how to use R in R studio. Oh yeah. And I'm a very I'm a mechanical engineer so I'm very visually oriented. And just having that stupid variable explorer there is just like it changes everything for me because I can highlight a chunk run it see what happens when I'm because inevitably I'm a horrible it is neat in R Studio you can like literally select a line that you want to run like highlight and run. I think both you get both concepts whether it's R Studio or a Jupyter notebook. I mean that that ripple idea of being able to like run chunks, cut a cell and run it. Like for me like even a lot of times I'll develop in in a Jupyter notebook and then put it into a Python script. But like when I can, you know, again, you're doing API development like or calling from an API, you don't I don't want to hammer that every time I run a script. Yeah. And let me just like call that into this cell. Now I can work on everything downstream of that. Yeah. Yeah. Well, and just like for me, a lot of it is debugging because I'm not a good developer. So there's inevitably going to be something wrong with it. Yeah. And so it's like if I can copy and paste something from you know uh which this is how I develop generally stack overflow or from uh bard or gbt and throw it in there and then okay well how do I I know what I want to do. I know how this works generally and I can start debugging it line by line and saying okay well this is where I need to change the for loop or whatever it needs to be right. Um, but I wish there was a better Python ID natively just like out of the box where I didn't have to go in and customize my entire thing. You and I still got to sit down. I mean, the Python the Python extension in VS Code is pretty good. Yeah. Yeah, that's really good. I mean, if you want something that's similar to R Studio, you should explore, download, and just play around with Spider. Spider is actually kind of similar to R Studio. It's laid out and we can put plots up. PyCharm is honestly my favorite one. Pycharm is really good, too. Yeah, just because it's it's straightforward and easy to set up. You're using multiple things though too. I mean like as soon as you want to start using multiple languages like you know VS code the extensions but what's um you're saying what's your evolution? My funny story is I didn't know a lot of Python programmers in the oil industry for a long time because it just it was kind of a small community. So so what I used in grad school I just wrote straight in Vim. So I use like Vim Windows and I just saved like pies and you knew how to exit Javas. So I literally Yeah, I know how to exit Vim. Yeah. [laughter] escape colon q. Um so um if you've got or wq so you do save it. Um so if you've got just like gimm like this like just a basic very basic editor which actually is a great tool for opening big asy files. So it's it's just for doing that you can right click in windows and open giant asy files. I think I've actually downloaded that when I was at RDS to open these giant CS we went through every [laughter] and Vim can do column edit column by column edits which is really nice and things like that. So anyways, I used just like straight Vim Windows for like 10 years for a long time. I was very resistant to going into any IDE. And so when people watched me code, I would just code and code and code. Then like I I would just have to run it and if it worked, it worked. And if it didn't, like I got to figure out what the air messages says. Like I had no debugging capabilities. And so I did that for a long time. And I think it's kind of like a school of hard knocks thing like, oh yeah, that that sort of hardened me and made me pretty good at typing things uh carefully and and reading my code and debugging on the fly like and knowing what I'm writing. So I didn't get really reliant on that. And so what what broke me was not that long ago Sean Sean Alo we were talking about he showed me his setup in VS Code. I was like oh you can just like take 5 seconds to create a virtual environment. You don't have to go through this whole process of building it on your machine and like having you know whole package setup and everything separate. He's like yeah you just you just literally say what version you want and and and then you can pull up a terminal and run it in it. I'm like holy cow. So, I already had VS Code in there. Um, because I really like the the ability for it to log in remotely without having to go through PowerShell and all that. Um, so there was some some usefulness there um that I was kind of sort of using it for and then he showed me that and then I started diving into it and looking extensions and so now I'm a VS Code guy. So now I use it. And you had co-pilot the Git. Yeah. Have you done uh GitHub copilot yet? No, I'm still very resistant to people to to having somebody inject uh you know some really like an LLM into my [clears throat] code and and have it potentially I don't know if it exports or not. I'm sure it's runs native, but I don't know. I'm very resistant to to debug tools also just because I'm a little bit weary of of how making myself overrelying on them. Yeah. And so I'm still kind of have that that old school mentality. I like to write out. Yeah. If you didn't have debug tools for 10 years, that's going to be a hard he sent me he sent me his like baseline code. I was like, "Ah, it looks good." And I start like going through like all right, we do this, do this, do this. He was like, "You're not going to run it?" I was like, "No, we're just going to write it and we'll figure it out. Like it'll it'll it'll run or work or won't work." And then it ends up, you know, I I barely experienced what he was doing. So, it just, you know, it ran and he was just like, "Ah." [laughter] Yeah. That gives me so much anxiety just hearing you say it out loud just coding lines and lines and not ever like it actually prepares you really well for working at Spotfire because Spotfire debugging is horrendous when you're writing data functions in Python um and in R even. Yeah, I mean you don't get really any good feedback. No, you don't get any feedback. I mean the if you turn on the debug tool um you get a little bit more like you can at least see print statements. I didn't know that for the longest time. I was like how do I print how do I print in Python to do like basic you know debugging? Um and so so yeah, so I you know you spend enough time doing it and you get you get kind of good at what you're doing and get really careful and and you can you can write a lot of uh really clean code like that. Um I use Beekeeper for my SQL ID so I really like it. Um it is it is open s it's it's open source and it's really available but I we like pay for the developer version. I'll keep it supported. Does that do like auto formatting and some of that too or it does a little bit. It has like uh format magic. I don't really ever use it because um no I again this is part of my I just like writing stuff out you know and I like writing in the format that I want to write it in. Occasionally if I get if I get really lazy I'll use chatgbt to write really long queries and be like or I'll write I used to write Python code. I used to write Python code to write SQL queries. Yeah. So I would like okay I got to loop over this annoying you know thing over and over again to create this view or to make a to make a certain um uh query. And so I would do that also, but chat TPT's kind of changed that. Like I can format things. I can copy a list of things out of Excel and like make this a Python dictionary, you know, like I don't want to do that. Yeah. Yeah. 100%. [laughter] Yeah. No, that's or JSON. Like make this a JSON, right? I need all these different fields. Write me out a JSON template for this. And I'm like crazy. Also fantastic for documentation on code. Oh, amazing for documentation. That's my favorite. I can like I I could know what the code does and be like, what does this code do? So it writes out some documentation for me. So if I go back later and be like, "All right, so I know why I did this." Because there's lots of code that I've written and I'm like, either I look at I'm like, "God, that was so smart. Why can't I think like this? Like [laughter] I've forgotten that I did this." Comments is like a love letter to your future self. Exactly. Right. Yeah. Exactly. And then and then there's times it's like, "Yeah, this comment saved my life." Yeah. Yeah. [laughter] Oh, for sure. That's uh that's one thing Dave taught me when I was in grad school. He was really good at commenting and very good at at documenting and writing things out. And so that taught me early on like how to do it and what level of robust you need. To your point though, using a really barebones editor like that, it's way more necessary, too. Yeah, [laughter] for sure. All right, jump into this. Yeah, we've got a few minutes left, so we'll we'll end it as we normally do with the speed round. We'll just pepper you with some questions. Quick one word, one sentence kind of answers. Okay, you got what's your uh first one? Yeah. What's your favorite cloud provider? Oh, none of them. Yeah, fair enough. Great [laughter] answer. Um, what is your what's top uh either top or just recently favorite uh book that you've read recently or um or paper for that matter. Uh let's see. I feel bad. I don't remember the name of the book. [laughter] It's a venture capital book. Um yeah, there's a venture capital book I read. It's like blue and orange. And I and and I know it was a really good read about how to build a VC and how not how to build a VC, how to how to raise VC money and how to build a startup. And it introduced me to a lot of business concepts around equity and things like that that I um that I know now. But yeah, I feel so stupid for not knowing the name of it. [laughter] People will recognize it. Maybe we can uh tag it in the comments. Yeah, there you go. Um what's your favorite open source project? Oh, um pandas. Is that is that basic? Is that the pumpkin spice latte of of Python? I mean, so it's just so powerful. You can do everything with it. It's amazing. Have you looked at polars? Uh, I haven't. I've been I've been told to look at polars a few times, but I haven't explored anything either, but I mean I didn't get stuff done. Again, my data is not usually big enough to where it's a big constraint, but I can make things really fast in Pandanda, so I haven't had like ah, this is too slow problem yet. Favorite video andor board game. Oh, solon. I will play that any day of the week and I play I had been playing it online quite a lot so it's a really fun game. Nice. And advice. What's that? You want to do advice? Wrap it up. Best piece of you go. You go for it. Yeah. What's uh what's what's some advice you give to somebody either looking to move into energy tech or kind of starting out, you know, in the the development programming world that wants to kind of coming into the energy space. Yeah, I think two things. Uh, go find problems to solve and solve them as fast as you can and show people how you solved them and get feedback. Like that feedback loop, I know people say that all the time, feedback loop in programming is really important. I'd also encourage you to find, I say this almost every time I've interviewed, find mentors, like find as many mentors as you can, quality mentors as you can. Get to know them really well and they will be an invaluable resource for your entire career and they're super important. No. No. That's a great way to end it because it's well and just like with our generation in the energy space, right? Like there are so many guys that are retired or still, you know, in management or whatever that have so much great experience, especially in all with all the nuance [ __ ] that we have to deal with in oil and gas. Yeah. That like let's make sure we lean on them. Exactly. Yes. We make fun of them, boomers, blah blah blah, but they know a lot, right? Like they still have a lot of information that they've seen some [ __ ] They forgot more than you know. Like it's it's amazing. Like it's they know a lot. Yeah. Awesome. Appreciate it, Andrew. Thanks for being on. Thanks for having me, guys. Where can where can people find you? I'm mostly on LinkedIn now. Um I'm I've I've uh since deprecated my uh Twitter on on account because it was taking up too much personal time. Um and so I've uh put that to pastor. Um so yeah, mostly LinkedIn. I'm around a lot at industry events and things like that. And then of course you check out uh forecast and forecast does have a Twitter page, LinkedIn page and forecast.io if you want to check us out. Number four. Number four. Thank you. Yeah. 4Cast.io. Um but yeah, if you ever see me somewhere, just um come up and chat with me. I'm pretty open. Cool. Appreciate it, man. Awesome. Thanks guys for coming out.