Welcome to Energy Bytes with John Kalfayan and Bobby Neelon. Your essential guide to the intersection of data and energy. This podcast dives deep into the world of energy, shedding light on how data, AI, and technology are revolutionizing this sector. Each episode equips listeners with insights into the most efficient tools and resources, paving the way for a data-driven future in energy. From technical nuances to broader industry trends, Energy Bytes offers an unparalleled perspective on the evolution of the energy industry. Join us as we decode the algorithms of energy, one byte at a time.
All right, guys. Welcome back. Another exhilarating episode of Energy Bites this week. Got myself John Calfan, my wonderful co-host Bobby Neelam, other Rad Dad. We got a new Rad Dad joining the club, Jeff Bernard, the uh [snorts] manager of digital at Ereon, which he just informed us is basically the all things tech position. So, that's why he's here today, but welcome to the the podcast, man. Thanks for Thanks for having me. Yeah. Happy to be part of the Rad Dad club. Yeah. It's It's a good club, man. We're just discussing the joys of [laughter] parenthood and sleeping and Yeah. Sleep schedules. All about it. Very important. Absolutely. Especially when they're little. Little bit harder when they get older, but uh rocking my Slobberin Hog billboard today in uh delirious hopes of of us maybe pulling a random win out against LSU this weekend, but best of luck. I'm not holding my breath. I'm elated that we started out and I know where we're at with the season, so I don't get any expectations. Um but speaking of Louisiana, you guys have a Is Is that your main office in Yeah. So, corporate corporate is in Broussard, Louisiana, and then we have South Texas. We're pretty much over the South all over the South. Main uh shell plays, um Permian Basin, Haynesville. We were involved in the Northeast at one time, um but it's it's too cyclical. Yeah. Yeah. Well, that's that's a long long way to try and manage from It is. And we did it for a while. That's actually where I started, but uh yeah, we're focused in in the South for now. Cool. Well, we'll get into to Ereon, but kind of give us, you know, we normally ask everybody kind of How did you What's your background? Kind of where Where did you grow up? How did you get into energy and or tech and end up, you know, kind of at at Ereon at this point? Yeah. So, [clears throat] I started in uh as a liberal arts major in uh in college and you know, graduated and needed something to do and so I decided to go to work for Areon and moved up to Ohio, I think, yeah, Ohio first. And worked the Utica gel play. And so Chesapeake had moved a bunch of rigs in from the upper Marcellus and it was trial by fire. Like go up there, figure it out, like get some reins on this thing. I think it was like four rigs at the time. And so I managed that and then What what year are we talking here? That was 2012. Okay, good. So I was 22 but Utica exploration back then. Yes, yes, when Aubrey was [clears throat] at the helm, it was like full bore, right? And so fun times, man. Yeah, they really were. Real fun. And so then I moved to Pittsburgh from there and kind of managed things out of there as well. Started doing some rig to rig sales as well as operations. Hired a good ops manager. I'm not inherently an ops manager. And so that kind of led into city sales and Chesapeake was sort of my, you know, first big account. And and again, I want to remind you this is the Aubrey days, right? So Chesapeake campus, Aubrey days. Really cool place to be and start out. And so sold to them for a while then wound up in Houston managing a Hess account and then sort of from there continued to do the corporate sales thing and meanwhile the whole time, you know, I'm coding nights and weekends, right? Started with WordPress sites and stuff like that. Just wrecked, completely wrecked WordPress site. Like build it And and you didn't start any of this until like you were working you decided to learn this stuff while you were working. Yeah, so I guess backing up a little bit, I learned like Dreamweaver in college and like Photoshop and Illustrator, right? Cuz liberal arts major you're putting together like Right, so what was the degree was it? It was in advertising and you exposure to to lot of those creative softwares so to speak, but dude, I remember I think it was in high like middle school or high school uh taking and I got like media publishing or whatever the the stupid name for media graphics was back in the early 2000s and uh I remember like we Dreamweaver was one of the things that we were learning and I remember seeing the giant book and like you know the instruction manual of Dreamweaver was like man, that's intimidating and then you start playing around like holy [ __ ] I can build websites. Yeah, that was such a cool thing back then and like the coolest. Yeah, yeah. [snorts] And and so, you know, it really didn't I mean I I was I was good at Illustrator like Illustrator was my go-to, right? And so, but but all that kind of taught me how to interact with software, right? Because things back then still weren't where they are today, right? It was still like a lot of you had to like pasting codes here and there and so you kind of got a feel for it. So, you know, fast forward to Houston again and uh we were having some trouble, you know, trying to get some projects off the ground internally. Uh there was IT support issues and so I was like I'm you know, I'm going to take it over. Just take the bull by the horns and so I found myself taking over just low-level IT stuff and then kind of worked up from there um and then I'm like well IoT started coming around, right? And uh like Particle and all of these companies, I think Hologram which is like a SIM company you know, started making bandwidth a little bit cheaper, little easier to do stuff. So, started messing around with some of that stuff and then um I was like well, why can't we connect some centrifuges? Like right, the biggest discrepancy typically um whenever you're like processing solids control cuz that's what Arian does on a rig is that you do a end of well recap and so it's like what happened? And it's word of mouth. It's Right. Somebody was writing on a spreadsheet Right. Somebody's recording Right? If [laughter] that. tablet, not a not an electronic tablet. And so you have you [snorts] have this data being entered from the field, and it's like, well, how do we get it to a point where, you know, we can see the state in real time? Yeah. And so you keep moving forward iteration after iteration, you you you know, have to start battling with PLCs, right? So you start learning this whole stack of equipment, from hardware to software. Yeah. And then you start finding like-minded operators. And then things start evolving through this whole time. Like it's it wasn't like a straight shot, right? Yeah, never is. It never is. And and then you find the right operator, and you start getting the right equipment. And then you're starting to integrate with their IT systems, right? And their real-time streaming. Yeah. And so that's kind of been what I've been focused on, and then we're working on some other new products, uh connected products as well. Okay. Um but it what's interesting is that as a service company, a smaller service company um doing it from the ground up is very hard. Uh and so I don't suggest doing that. Yeah. [laughter] I suggest finding like the right vendors and the right equipment to like achieve that, you know? Yeah. No, that's uh [snorts] it's funny because a lot of people, I mean on the software side, people have the same you know, same exact battle. Do I build it from scratch, or do I use, you know, somebody's SDK, or do I just use full third-party SaaS product, right? Regardless of whether it's, you know, machine-to-machine messaging or authentication or whatever it may be. And it's a real like that's honestly one of the big things we wanted to kind of try and highlight with this podcast is that like there's a million different ways to end up with the same result. Right. What a lot of people, my learnings from this have been, you know, whatever works best for you is typically the best path. Whether that's, if you're trying to get something spot like, you've only got three knobs to turn on the project management, you know, wheel, and it's cost, speed, and quality. And so, depending on which one of those is most important, one of them can potentially get you there. but that absolutely makes sense to me. Yeah. And so, that's like, hey, if we need something fast, you're probably going to go with a SaaS offering versus if it's not as critical and we can take our time, then maybe we'll do an SDK or just hard code it from from nothing. And so, it's a it's a very real problem. Um before we get too deep, back up, tell the describe what you guys do um at Aereon for the average persons that might not be as familiar with the drilling side and So, we're on the drilling side. We uh process drilling mud uh through a process called solids control. Um you're basically taking what's coming out of the well bore, putting it through equipment that's spinning at a high rate of speed. You're separating the fluid from the solids, and then allowing them to uh uh basically recycle the fluid back into the drilling system while keeping the mud in specification that, you know, they've set for the well. Right. And then you also do analysis on the solids as well, right? To understand where you're at. So, even set back, I mean, I don't know how many people like and stuff about drilling mud. Yeah, that's that's a good point, too, right? So, you know, when you're drilling you're basically you've got a giant pipe that you're that has a bit on the end of it, and you're pushing fluid or drilling mud through the center of that pipe, and it comes out the bottom of it, and then comes back up uh to surface between the space between the pipe and the actual earth, called the annulus. Um and that's what these guys are looking at and separating. And so, instead of that just going into a tank and it being waste, they separate the physical solids out of it, and then they allow the operators to recycle it. Is that a Yeah, that's a good that's a good description. And one thing that they used to do is they used to just dump it Uh, like into big fields and And do a process called land farming, but you know, over the course of probably the past 7 to 10 years, that has been phased out obviously because of environmental concerns. And so, uh, our part of the industry has grown pretty significantly, you know, and so, yeah, we basically handle everything that's coming out of the well [clears throat] bore. And we process all the fluid, right? Take the solids out, and then we run tests on on the fluid called a retort, which allows you to see the properties of the fluid to make sure that you're processing everything effectively. Okay. Yeah, yeah. I mean, I think you can just get back to criticality. I mean, cuz even like the mud weight and everything matters like that you know, to prevent blowouts, right? It's one of the most important things on on the rig. Yeah. Yeah. So, when they talk about mud weight again for for those of you who aren't familiar, they're talking about the the fluid properties that they're pushing into the well bore, and those matter because as you're drilling through the earth, you come across different formations that have different pressures, and you want to make sure that the pressure coming out of the bottom of the [laughter] the drill bit is not higher than the pressure going into it, which would cause a blowout. And so, drilling mud and it's all of its chemical and fluid properties are incredibly important through the drilling process. So, it's So, I think this starts to then highlight sorry, probably like the importance of some of the real-time aspect of what you you guys work towards and have implemented in your work. Exactly. So, you know, the way that people reported this, historically, you have what we do, which is solids control, and then you have the mud company who controls the mud. So, these are two separate companies in charge of basically one process, right? mud engineer out there, yeah. Right. And so, there's you know, it really depends on the relationship between everybody on the rig. You have some rigs where everybody's like on the same page, just like any other workplace. Sometimes they're not, which is difficult, and uh, but what we're trying to do is bring transparency to the process. Yeah. And the way to do that is rather than having a human report what's going on, we have our equipment reporting what's going on. And this is nothing really new. I mean, you have SCADA systems everywhere, right? Um and so what we've done is just basically plugged into PLCs and we're transmitting that data where the operator's cloud is. Yeah. And I guess maybe ours So H 50 is something that I'll probably pull us back a bit. So can you talk about what a PLC is? Cuz I don't think we've Yeah, we haven't done that yet. So it's a project. Uh
Or uh process logic controller, right? And so it runs code from the various systems and it takes it tells uh you know, a gearbox to engage or tells uh in in the case of our equipment, a bowl uh the centrifuge bowl where the fluid goes through to spin, right? So it it it basically has it's the computer for the equipment. Right. It's It's the brain for the industrial But it also pulls the data out, too, right? I mean, or it or creates data It It creates data and and there's different there's serial uh there's like modbus. And again, I'm not like a uh control specialist, right? But um beh- after that, that's the stuff that I handle. I work with like control systems companies to get it Yeah, to get it out. hardware. Um but that controls the equipment and there's a lot of valuable data there. There's like run times, there's RPMs, vibrations, there's a lot of uh processes that the PLC monitors Yeah. that we're able to transmit to the operators and also ourselves to know if there's an equipment failure. Mhm. Right? If uh equipment's vibrating too much, right? Because if you have a very large piece of spinning metal, you want to have it balanced. Yeah. It's very important to have it balanced. what like your washing machine, old school washing machine Yeah, exactly. Like and then put it on steroids. Right, exactly. Yeah, and then also if if you don't know the data coming out of it within a pretty short time frame, something really bad could happen downhill. Like the the criticality, you know, it's it's funny because it's like the process itself Yeah. of what you guys do isn't necessarily overly complicated. No. But you take that and you put it on a drill site with all the externalities that come with drilling and the urgency and the cost and the risk from both safety and environmental perspectives, it's like a whole 'nother ballgame. And I think that's again, one of the big things we hope to highlight for the tech community with this podcast is just like a lot of the stuff that we do in the oil field isn't necessarily, you know, new tech or new things. It's taking existing stuff and figuring out ways to oil field it. That's right. work [clears throat] in these specific scenarios under these specific conditions with all these constraints and criteria that it has to meet in order to do to operate safely and Yeah. And it's not also not that we necessarily want to be slow to adopt things, but we almost have to be. Things have to be vetted before you can just implement them where they're again, there's such high stakes. Yep. Um monetarily and just physical world. And I definitely want to make the distinction. There's a difference between monitoring and control, right? Um we monitor, we don't control. We have people that are trained on the rig, you know, [snorts] all certifications that are manipulating controls, right? Um but we do monitor. And when you start getting into control, I know I I know you've had prior conversations about rig to cloud Yeah. control automations and it's like very difficult to do for a variety of reasons, right? And so we definitely don't we don't control it. But we hope to do that at some point. Yeah. And that's you and I have had conversations about that in the past. That's where I met you at. Yeah. I have so many. No, I I think that's one I think that's honestly just a natural progression, right? Not just within the oil field, but it makes even more sense in the oil field just because of the additional risks and stuff associated with things, but um you know, I think that's that's why when I first started talking about I have so many learning about the edge stuff, I got so excited about it because you can it's very easy to see how the dots start connecting and leading to hey we were doing this on literal paper and Excel sheets to were monitoring everything in real time to okay now we're monitoring and then reacting based off what we're reading from those monitors in real time without a human ever having to touch it right. Exactly. It's going to take time. There's a lot of things that have to be hashed out. No one has any you know big ML models that are 100% reliable or anything like that but be the vision but you got to correct you got to work to it. Yeah, I mean we're I feel like the industry as a whole is [clears throat] understands it at least and it it's not it's not this crazy like exotic theoretical thing anymore right? It's like okay we can see how these things compound with each other in these different texts whether it's Edge or just IOT in general. Yeah. And then you can throw Starlink on top of it and right like it's you're solving all of the kind of pieces and once you start putting all that together you're like oh this could really be interesting. I think what's interesting about that is you have you know um you have existing systems out there. It's not like you're having invented from the ground up right? And so it's not I think there's a tendency to want to over complicate things. That's where I was initially right? Um but the more you go along the path of like trying to figure these things out. I really do feel like less is more in a way. Um you know we started with some very elaborate modems and stuff like that tried to self-develop some stuff. It was too much. Uh just it it it was it wasn't that it was too much it was kind of unnecessary and so It's also are you an infrastructure company or are you a software company or are you Arian? You mean what what do you what is your core business? Yeah. And so so you the best thing to do from our standpoint is align yourself you know with a robust industry like if you're going to go with an IOT modem right? Go with the most robust modem that you can find, right? Yeah. And then um something that's you can expand on, right? Cuz once you install it in equipment, [laughter] right? You don't want to reach capacity as soon as you install it. And then from there, uh you can keep expanding the operations, but you want like as few components as possible. So like your edge device running MQTT, right? Running probably Ignition Edge or something like that. And then you're pushing data out. Super simple. Okay, so So here we are. We're working up the stack. So we got the PLC and now we're talking about your edge edge device. Um yeah, let's dive into that and then maybe dive it cuz again, we we you know, John and I are pretty familiar but I don't think we've really gotten into No. you know, this kind of edge stuff very much. Maybe with um uh Haliburton um Frederico a little bit, but like I mean, let's talk about edge device. Talk about MQTT and like how that's different than some of the other protocols. Yeah, I would even say back up a step further and basically [clears throat] start from the bottom, right? So the sensors to the PLC and like cuz that's another um direct camera moment uh for all the tech people in the world. One of the biggest complications on any oil field operation is that there are potentially dozens of different vendors on the same job all monitoring or pulling data from different things in different ways in different formats. And that's where things get really interesting from a from an operations perspective because it's all disparate data and different people's systems at different rates at different times and all that. And so that's why in my opinion it's taking us so long to kind of adopt a lot of these things even just as simple as monitoring, right? Not controlling or automating, just monitoring is because there are all these different protocols, these different structures. Everyone wants to is hesitant to uh have someone plug somebody else's stuff into their stuff because what if it breaks or if there's anything malicious or they're going to steal their information, whatever. Um so I like it's it's really cool that you guys have what you've or have built what you've built so far because of I mean, that's a big hurdle out of the gate, right? It's like Right. You aren't necessarily generating your own data if you don't have input from some of these other systems and so So, kind of walk us through from like base layer, you've got your sensors up into the PLC, then to the edge device, all the way up to the kind of the cloud side, the Yeah, so like just generic architecture, right? Um you have your sensors and then that's being pushed to the PLC. The PLC is running all these interactions with it, right? And so you have a set you're not going to acquire everything from the PLC cuz some of it is just Yeah. it's not it's not vital, right? So, you define what you want to acquire from the PLC. That goes into your edge gateway, right? And that's usually a modbus connection between the PLC could be modbus serial. Uh it really depends and that's the other difficult part Yeah. about oil field equipment is if you're doing this like uh after the equipment's built, in a lot of instances, you know, you acquire equipment through whatever and then you have all these different PLCs, right? So, nothing's the same. Imagine like Windows 10, Windows 11, Windows 7, right? So, you're having to sort of funnel all of this into your gateway, right? And then you have two paths. So, you can push to the rig or you can push to the cloud. We do both um because we want to be independent so that we can have control over it. Uh and we provide our own connection. Um you know, trying to run off of the rig Wi-Fi, it's a lot of red tape. IT doesn't love it. So, you have to It's It's another dependency, right? Like It's another dependency. have no control over which you can a funny story, early on both sides of it, I think. Early on, we, you know, uh you know, get the get the green light to connect to rig Wi-Fi and then we had uh sort of a segregated hotspot by itself on it its own network and uh people are plugging it, unplugging it [snorts] to plug in their cell phones. Like different people on the rig, right? So, you're trying to roll out this project and then it's getting unplugged. So, it's like hotspot was connected to be USB or something and they want to plug it in. Yeah, like the dog house or something, right? [laughter] And so, you're having to battle stuff like that. So, that was when we sort of made the determination that okay, we have to be completely self-sufficient. We cannot rely on anybody else. Yeah. But, our own comms. And so, you know, we have you have your edge device that has a modem built into it, right? And so, you can push uh your data to the EDR system, which is the drilling recorder. It's like the server on the rig. not going through the internet. Is that on it? That's local network. Yeah, so that's locally on the rig. You're sending it, you know, to the rig system. [clears throat] That's being done with whatever they want to do with it, display it on the monitors on the rig, whatever. And does that become part of the WITSML stream? It does. Yeah, so it gets aggregated into the WITSML stream. Okay. Yeah. So, a few things there. EDR for those who don't know is basically a drilling rig's black box as compared to the airline industry. Uh it's where all the data goes and ends up most of the time. Um it's something that the completion side has yet to figure out and uh Bobby and I are intimately familiar with that in our past So, that is a luxury of upstream careers of drilling specifically. Um you know, drilling they Pason, I believe was the first one that introduced that back in like the '90s, early '90s and it took another 20 years for completions to be like, "Hey, that's a good idea." But, at that point it was too late because frac was [clears throat] blowing and going. Yeah. But, uh so that's what the EDR is and then um what was the other one I was going to mention? The uh Well, WITSML probably. WITSML, yes. I'll let either of you get into that cuz you're both more familiar with Yeah, I mean WITSML is basically a a data standard for transmitting drilling uh data. And I actually have WITSML for completions now, but no one's really adopted it. Um [clears throat] and say what you want about it, it's XML-based generally. I think you they can technically push it based on if you want to, but most people it in that, but Yeah. But, I think most is pretty standard it comes out in this XML format, but you know, whether you like it or not it is a standard and people know how to develop against it and so it's allowed the Corvas of the world and different, you know, vendors to actually develop against it cuz it's a standard and they can do things with it. Look Look what we can do when we have data standards, guys. Let's figure it out everything else. So again, I mean what you guys sent to it is just one piece of it but then there's all the different pieces but it's a central place, you know, that stream is where, you know, people can get the data they need in real time. Right. And that allows That allows the You want to have multiple streams, right? Because or multiple avenues for data acquisition because it's not guaranteed that they will let you plug into that the EDR, right? Like it's going to be operator specific, right? And so you want a way to be able to plug into say something like Corva or something else, right? Like I imagine a future oil field where you have like Who's going to build Zapier for the oil field, right? Like who's going to build Are you going to build it? [laughter] Maybe three of us need to cuz John's talked about it. I've been I've been like foaming at the mouth over this for like a few years, you know? Like just aggregate this this layer that you could plug into and then send data to whatever platforms operators are using. No, I think we're actually finally I when Bobby and I first started talking about that was a few years ago and uh you know, I started looking I was like, man, nobody has even Nobody didn't even has APIs that are you know, disparate exposed or anything like that. No one wants to work together or partner on [ __ ] Everyone's still super secretive about everything. But over the last I think honestly COVID was really the big kind of turning point for some of this stuff. We've started seeing more and more like uh Coldbore and uh Corva partnering up with stuff. And like that's exactly what the industry needs is when we can all specialize on the thing that we do really well and let someone else do the thing that they do really well but then we can share and integrate with each other. Yeah. The possibilities get so much greater. Um but yes, let's we can we can chat after. I thought [laughter] that I would I I mean it makes so much sense because [clears throat] there are so many workflows in the oil field that are just disparate for no reason. I I mean I imagine it like it would be um and I know not everybody is using cloud platforms. Like I understand people still have their own on-prem stuff. Yeah. That's fine. But uh you know, you sign up for a commercial software and then you go get your API key and then you start start working with the API. Like that's what I hope that the oil field goes to. Yeah. You know what I'm saying? And so that's sort of what [clears throat] we're planning for. Like whether that's 5, 10, whatever years down the road that's where I think things are heading. Yeah. Yeah. Yeah. I think the operators help too, right? Like being able to have operators in their contracts say you must have an API or you must be willing to share data Yes. or even let people plug into your box. They're not trying to infect it with the virus or steal your code. Not trying to infect Trying to make it easier for everyone. Yeah. Yeah, so and I so I think you know, working our way to the second thing we've we've skipped a little bit of a step. So I do want to go back to using EDR, but then also you're saying also you can push to the cloud platform. Right. Um, and then we can get into all that stuff cuz you know, John and I talked about APIs and some APIs are not very good. They aren't. Um, so it's a matter of like, you know, we've said before maybe I just want you to just dump a CSV in a FTP folder at this point cuz it'd be easier to get than getting out of your copy API. But Right. But let's just step back until we get to that point. Um, so you just the edge device is sending can send locally like on the rig, but then you're pushing up to your cloud platform. Yeah, and so sort of how that works is that is another component that's independent, right? We originally had a fully integrated solution. The company no longer provides it. That's another thing to look for is when you're getting hardware, make sure that the road map is set up long-term so that you don't get rugged on the Yeah. on the device, right? Cuz then you have to start ripping and replacing. So, try to keep things modular, keep few components, and to your point about the MQTT that the the beautiful thing about MQTT is you're not wasting a ton of bandwidth. Yeah. It's sending data whenever something changes, rather than It's a push rather than having to pull it. Exactly right. Yeah. And so you're not you're not pinging, you know, your data every second to check for something new. It's sort of like a webhook for any developers out there, is how I view it. I know it's a little bit different, but I'm trying to think what the JavaScript is. Yeah, I got it's Um it's not a you know, it's a I think it's a socket essentially. Right. Like a websocket. Yeah, websocket. That's what Um But yeah, but I mean there's a couple different protocols. I mean it'd be interesting to know what you guys cuz I know like there's some of them where you can guarantee delivery. Yeah. And then another one where you if say you got a super high frequency, you can send it and but be like it may or may not make it there. Yeah. Yeah, so we have like an MQTT platform, basically. And uh you know, it's plugged into the edge device. And so you set the parameters, your dead bands, which is basically like when do I want it to send a piece of data? Yeah. And then so data's sort of like trickling up as it's changing. And so uh that keeps your bandwidth cost lower. Mhm. Which is very helpful, [clears throat] right? if you lose connection? Well, you try to get it back up as fast as possible. No, no. And and and it keeps kind of a leading question. I mean just that's what I mean MQTT the beautiful thing about MQTT is if it if if it if you don't have connection, what it stores it It stores it locally and then pushes it up whenever it gets connection again. Yeah. So again, like you're you could sit be sitting there pulling and never get anything, but like cuz sometimes when you have those polling type systems, like they're polling it for a certain timestamp cuz it knows what time it is and then you lose or you have to go back and repull everything. Like this will just store it until all right, now we have AT&T is back up and then that whole packet of data is gone. That's right. Yeah. So you can there's different data retention time frames, but you typically retain it on the device and then whenever you have a live connection again, it'll push it back up. Yeah. Yeah. Bobby's Bobby's speaking from a from experience [laughter] on on side of that. Yeah. Uh It's nerve-racking sitting there watching it drop connections and you're like Yeah, but we we you know already have to Especially if you don't have MQTT. You were running like a polling type system and it's just like they didn't have to have to go back and get stuff off of you know off of the device or you know just That's why I'm a big proponent of uh if you're not going to self-develop things to get a a very robust platform Yeah. for that. So, a lot of that infrastructure's handled so you don't have to have a massive team to handle infrastructure. Well, and it's tested [clears throat] by other people, too, right? Like the risk it's de-risked to So, so can you speak to that platform? I don't know I don't know how much is proprietary or not. They're So, uh yeah, a lot of it's proprietary. I mean, it's pretty standard stuff, you know, like Ignition Edge. Everyone knows Ignition Edge who's in the automation controls and there's a lot of power in that. The real sauce is like the algorithms behind it that you can develop uh on. So, are y'all running So, this is Inductive Automation's Ignition Edge version? Are y'all running Edge on or not on your Edge servers? Yeah, exactly. Yeah, and and the beauty of that is uh it's low code. Uh and and that's really cool because it's very supported. You can uh basically copy and paste projects very quickly. And then Ignition is also just like a big industry standard, right? Like everyone in industrial [clears throat] automation knows Ignition, uses it. Right, so there's no propriety to that. Yeah. No, it's a it's a it's something that until I guess really until I got kind of into the production and data monitoring space, I had no idea that that existed. And then once I got into it, I was like, "Holy [ __ ] everyone pretty much [laughter] uses it." Everyone. I mean, breweries, like nuclear power plants, like everyone uses Ignition and it's super cool and it just keeps getting better. Yeah. Yeah. Well, and they've got all the I don't know what they call their what acronym they use for their partners and and all of that stuff. But, that's the other big thing on the industrial automation side, right? Is like historically, there are all these like proprietary formats and stuff Yeah. sensor vendor built so they could basically lock people into their platforms and now that has finally started going away especially with people like Ansys and Ignition and those types of folks being able to basically make it it's almost like a Zapier if you think about it because it can read all the different formats and from different uh protocols and stuff like that. Um so are you so does that then push to the Ignition Cloud? Not Ignition Cloud. We have a different MQTT service um and so it pushes to there and then they have a very robust GraphQL API. Okay, nice. So rather than you know like a REST or anything like that you're able to get what you need in the queries that you build um from that API. Yeah. Well, that's good because I mean we haven't talked about GraphQL APIs um I'm very interested because one of It's really sweet. Yeah. No, that's pretty cool. It's just it you know you have to rewire your brain a little bit on it but I mean you tell me if I'm wrong. My understanding is because I've used it a very little uh cuz most people don't expose them especially in the oil field. Mhm. Um They have no idea what GraphQL But it's like cuz like traditionally with a REST you have like a certain end points that you can hit and then like so you have to hit three end points to get the data you need and then you have to combine them downstream. With GraphQL you can almost kind of write that query against those three tables or end points and get the data from one GraphQL call. That's right. Yeah. Yeah and and that's the beauty of it is like uh to your point rather than having a library of end points you have one end point like one pool of data and you're able to just fetch what you need out of it with the different you know parameters basically. structuring it in the query and doing all the joins and stuff. Exactly. Yeah. And so when you fish stuff back out like if you automate it from another system like something like Data Factory um from Microsoft or Logic Apps like you're pulling it from that API uh into another platform you're able to like dynamically change the parameters which makes it really nice cuz you could build a UI on top of that and you don't have to like do 100 end points. Yeah. That's slick. And then so that goes into a database of some sort. Yeah, so basically it just goes into the MQTT cloud, which on the back end of it it's like a SQL database, and then that's where the API we plug into there. And then we can push it to whatever other platform we want to, right? Consume it how how we want, which is really nice. And that's uh sort of my first thing to look for when onboarding any sort of new technology. Like they have to have an API. That was my first requisite, and then I learned very quickly, to your point, Yeah. uh you got to have a robust API that makes sense because an API is nothing if it's not robust and and well done. Absolutely. Yeah, I mean I had one and I wasted probably 3 days of developer time, and then turned out I couldn't get the data in the back end that matched what I saw in the front end. So frustrating. And I was like, you immediately think, "I can see this data point right here." And they're like, "Oh, yeah, sorry. Well, that vendor is off-boarded from our platform." And you're like, "You can see it, but you can't get it from the API anymore." And I'm like, "Then how are you serving it to the front end?" You know, cuz I want that. Like that's our API. [laughter] And you're like, "No, that's literally what I'm paying for." Well, what I what I built is totally useless now cuz we need data all the way back to the beginning of the year. And you're Yeah. And so I you know, I think it's uh asking a lot of questions is the main thing, and when you're find the the people who are willing the oil field's 24 hours a day. Yeah. So, when you're working with these vendors, like of course don't be a jerk, but you need them to answer the phone, and you need to have someone who knows the system that you've been sold. Yeah. And so that's another thing I've tried to align myself with. Just like when you're in the oil field, for the people that don't know, like you build these relationships with people, and they answer the phone, right? Doesn't matter really when, but they're going to answer the phone. And so I try to look for those same partnerships with vendors, whether it's a sensor or whether it's cloud tech, like answer the phone. Microsoft, it's not the same thing, but their stuff always works. Yeah. So it's good. Yeah, they're robust. You know, you can generally count on it. yeah, yeah. the independent components, you want people that like know these things intimately. You want them to even like in a you could argue I mean like Microsoft, whether you like their documentation or not, there is generally documentation for what you want. Two, you know, so you better It can be a and/or kind of thing, but you better have either someone who pick up the phone or somewhere I can go and get the answer I need and be able to search it pretty quickly. Um but I think it's something people undershoot and like in John and I love our open-source stuff, but like with open-source, it's on you. Like if you decide to implement it, now you can obviously do like the cloud-hosted version and then you then you have that support, but I think to your point like when in something's business critical, you better have some support on the other end of it. I think that's why oilfield IT loves Microsoft cuz, you know, like there's just that support system around it. Yeah, and I've heard a lot of conversations on this podcast that have gone back to Microsoft, but I really think it is true like most businesses run on Microsoft, right? Like uh as far as like Office 365. So once you're there, you're like not going to leave probably. There's really nothing to replace it in its totality of what it offers, right? Yeah, especially when they're coming in and offering all the operators infinite cloud credits to make sure they don't move to AWS or Yeah. And and Google. And and like I I sort of went down the AWS route early on, but I was like everybody's here, right? So if you're building like even internal apps with like Power Apps, like low code, right? Your user base is there. You're not having to like jump through a bunch Right. You just manage it all from there. Yep. It's beautiful. Yeah, even like you know, one of our new data engineers, um Sean, he he builds actually like PHP apps, but you you deploy it through Azure web apps and he easily ties into our authentication and so all the Duo authentication our IT set up is already just kind of there as a, you know, gateway into it and people can access what they need from the cloud, but it's all federated and it's easy to get to. I mean Yeah, I'm I'm excited about uh their partnership with OpenAI. I really tying it to the oilfield specifically. There's like a lot of tribal knowledge in the oilfield. Yep. And uh I know like LLMs and all this stuff. It's buzzwords right now, but after heavily using chat GBT, I can really see a lot of that tribal knowledge getting integrated into the workflows that we're doing, right? And that's one thing I hope to do is like sort of start working with getting context out of the data we're acquiring to the end customer from you know, Microsoft's cloud and their partnership with open AI and co-pilot and whatnot. Yeah, yeah, I mean just I mean just the idea of a co-pilot, I mean it obviously it started off like on the kind of the coder GitHub side, but I mean now they have just decided they have co-pilot for Word or Excel or I mean even just across the whole Microsoft fabric stack. I don't know if you how much you've looked at that. Yeah, yeah, it's sweet. that's going to be where you can use co-pilot to build your data factory pipelines and then your Power BI. I mean just the whole you know, cradle to grave. I mean the vision is great and it may again now let's see if Microsoft can execute on it or how long it takes them to execute on it. I would usually an if not when yeah. Uh or when not if, you know, kind of thing for them. They'll they'll get there, but um this is probably like the biggest data release they've had in a long time that I'm genuinely excited about. I mean like it's been a lot of it's like Yeah, piecemeal a little bit, yeah. But but as they always do, they start to figure it out and then they're like, oh, now we have this cohesive thing that works. Like Synapse was a disaster for a while and it's gotten better and gotten better and now it seems like, oh [ __ ] this fabric thing works out, this is going to be a game changer. Yeah, they've done a really good I mean there's very few companies that can compete with the likes of Microsoft and Apple and and those folks, but typically the bigger a company gets, the worse their That's true. support, turnaround, innovation, and all that stuff gets, but Microsoft has done you know, they're one of the outlier cases as far as software companies goes, where just because they have so much built-in network effect from Office. Right. Um and just Windows in general out of the gate, that they don't have to directly innovate, they can go buy someone, but the way that they innovate is by really truly being pretty good about seeing where things are going, quickly buying someone that's ahead of them in that space, and I'm figuring out ways to integrate it in every possible aspect across the the stack and stuff. I think that's the their feedback loop that they've got like Power BI, right? Like I remember when Power BI originally came out. I was like I like the back end editor having a GUI instead of having to hardcode stuff, which is really slick. But then it's like, but I can't, you know, just little stuff that I was used to like in Spotfire. Like was impossible to do it in Power BI. And I was like, okay. And then you read the stuff that they had a year later and like, oh [ __ ] this is like a much more complete product in a relatively short amount of time considering it's a you know, international release of a software product. Um, but I think that's one of their like big advantages, right? Is they have the network effect. Everyone is using their entire stack basically on a day-to-day in an office. And so it's just how do we plug in these new things and make them as uh as useful as possible. They've done a great job of really getting that feedback loop. I think the same goes for Power Apps. Um, I built a ton of stuff Yeah. from Power Apps and uh you always get asked in an IT role, hey, like we have all these spreadsheets, they're all serving the same purpose. Like, how can we from a C-level perspective, like how can we see all this data, right? And and so um I've I've built a ton of Power Apps and that platform has only gotten better. Yeah, it's it's really I mean we we've got a couple just released too. Like our production tech built them and released them up, you know, went up in the field loves it and What I wish Microsoft would do is buy Bubble because I developed like a field application for our guys on Bubble. Um and I I think that if they acquired something that was outward-facing, like a low-code builder on top of all the tools that they have, it would be a complete game-changer. I'm really hoping for that. Yeah. Yeah, because it's it's like then you would be able to give your customers, you know, easily True. True. Exactly. Yeah. Cuz that's the hardest part is like then you have to go build something custom for the customers. Right. But [clears throat] I'm a big believer of getting the data to whichever platform that they use, whether that's Corva, you know, AI Driller, or any of these platforms. Like that's why I've gotten things to where it is now. So, because I'm waiting for that the Zapier when you build it. Yeah. I'm wait you know, like we'll be first customer. [laughter] What uh So, going First, I don't want to skip this point because it's intimately important. I don't think the tech community understands this enough. So, I'm hard turn to the camera, but what we were talking about earlier as far as support um I I think we understated it to be completely honest. Like as much as we were talking about it. Uh you cannot work in the oil field if you aren't going to be able to have someone answer the phone when one of your customers calls you at 10:00 p.m. on a Saturday night. Um you know, you you might have 24-hour tech support where it gets pushed to a voicemail and then it goes into a ticket and like that doesn't work in the oil field. Especially when you're doing operations at the operations level. Um so, please be a aware and cognizant of that because it's it's very important. And just cuz you've got the best devs in the world, if they're not available or they're overseas on holiday and they're not available, it you're going to lose customers very quickly or not get them. It really is amazing like just picking how important just picking up the phone is. And not it's not even just oil field. Like you see it like all these small business people on Twitter talking about like if you just move into a arena where the other guy doesn't pick up the phone and you just answer the damn phone like Yeah. you could make a killing. Absolutely. I mean um There's something else I was going to go with there. When I was in sales, like I probably sold more by just answering the phone. Like I mean, I would think I was on Bourbon Street one time. Yeah. I'm talking to a company man. It was like during Mardi Gras. And like you're selling stuff then, right? But it it applies to the technology aspect too because once you get integrated Yep. and they're starting to rely like when you get a sticky product Yep. and it's data related and that dies, it's as good as your equipment being down. It's the same thing, right? And so it's part of the stack at that point. So it's like very imperative to answer the phone and fix the problem whenever there is a problem. Yeah, so especially I mean always but even like early on I mean like I know I think it's Combo Curve like when they came out like they they'd be back with you in 10 minutes if you send them an email. Like I mean it's like that was something you just don't you don't get that from Landmark and Erie like you know Halliburton like you know it's like if you just No. get on the phone like and then you're working through with stuff with people and you have if you put that first like if you got a startup you should put that first like I mean like it's easy to ignore but if you don't have good documentation or people to answer the phone like yeah you're screwed. I want to know y'all's opinion on or is there going to be a startup that replaces like the Toddcos and the like the EDR systems like is there do y'all think there's going to be someone that comes in and revolutionizes that space or that sort of just baked in? So my thoughts on this are interesting because it's more from the completions perspective but I'm surprised and this is actually kind of happened in the drilling space. I don't honestly know whether that happened through acquisition or uh or what but you know the manufacturers have all of the opportunity in the world right? The NOV's, the Dragons, everybody that's building equipment in the oil field has like you have 10 steps ahead of everyone else that's trying to go out there and money to do it, right? Right. And you know exactly what the customer like you have everything you possibly need to know except they're all huge and so innovation is not normally the thing that they're the best at but you know you're you're the ones that's actually generating the raw data from your equipment so therefore you should have the ability to then go do a bunch of stuff with that raw data. Right. Um but like I said those companies typically are bigger and they are much slower to innovate and a lot of times they spend they overspend they over engineer. Um and it takes a you know, look at Corva, right? Like people like that to come in and say, "Hey, this exists. We're going to piggyback off of that. We're going to do a lot more on top of it than just what you guys are doing today." And so I think I think you'll see like consolidation really around some of that. I I can't wait to see other companies I and there are some like AI drillers out there, right? I've I've spoken with them. Uh but Corva's made it really easy to go in there like their app store. Like they're they're making a hard you know, plug for for for what we're talking about. It's still a little cumbersome to integrate. Um I'm like build a WYSIWYG, you know? [laughter] Yeah. Like I want to drag and drop dashboards and and get stuff in there real quick. And uh and I think that they'll probably get to that. Now and I hope there's more beyond AI driller and all that for all the different peripheral services. Yeah. Without I mean I was just curious like what No. Like what what would what what does like zero to one look like in that space? Is Is there going to be enough you cuz I think to really replace it it has to be that much better or people say, "I'm going to move to it." Like um you can't just one to end on it and be like, "This is a little better." People aren't I mean you have to for them to you know, it can't be get off of like Wits 'n' Oil or these standards that they have like everything built off of and like we were talking about before the show like it it has to make sense for you to even invest the time and money to transition to that. Yeah. It's got to be a step change not a a additive kind of situation. Right. But I think again, I'll go back to Corva. Like I know the one of the problems we've run into is like we integrated but the operators we work for like it's you know, you work for operators you don't and once you don't and they're on something else then you have to figure out how to get back in. Yeah. Get well, get your data to their platform when they're not using XYZ company, you know what I mean? And so it's like um Corva's done a really good job at building this platform and I just hope that these other companies that are up and coming or the bump manufacturers and all these companies start building technology into their equipment. I don't know what the incentive is other than the operators are like we need this, right? That's an incentive. I just don't know how like a lot of these companies have so much market share that they kind of just you got to take what you can get. the the other problem of it too is it it's this it's a trickle up effect almost where it's like okay, we're NOV and we develop this new system that completely automates the drilling rig. Like nobody has to touch it. I in this future fantasy world. Um Well, so then NOV has to sell that to whichever service companies buying it. So NOV is going to want to make money off of it and ideally in a SaaS ARR way. And then the service companies also going to want to make money off of it because it's the new thing. And then then you have to take into account what the, you know, oil and gas market is, right? Is it up? Is it down? Because That's another good point, right? the intrinsic value of of what you're providing [clears throat] has to be so great that it's such a it's a legitimate step change in what things are doing, otherwise the operator just sees it as another cost potential like another rabbit hole we can go down, but oilfield typically treats data as an IT function and IT cost, not an additive benefit within each asset. And so that that has to it's changing as as we go. also, you know, I think people are going to our generation, I guess, right? We'll split the difference between you know, us. Um they don't find it all that interesting. Right? Yeah. And obviously everything the environment that we're in is not conducive to people entering the oil field. Um I hope people see it as vital. Yeah. Um I at one time very, you know, when I started and I didn't see a path for tech. I would thought about getting out of it. And then I saw some things starting to change and so I stayed in it, right? And I think it's going to take more of that. I don't know if there's going to be a ton of new entrants because of it's like not cool. Yeah. But hopefully that changes, right? Like we need it. Technology is going to be a pivotal part of it. I think we can make it like cleaner, better, all of those things. Uh and all tech's like really cool. Well, yeah. It's a really cool problem. There's so many problems to solve and so it's Yeah. if you if you like solving problems, the oil field is a great place to be because there are so many and it's not one of those where it's like hey, we made, you know, the manufacturing time of this thing 10 seconds shorter, so the company saves however many millions of dollars. It's hey, we're a critical piece in the the literal global supply chain of energy, which is not going anywhere anytime soon regardless of the source. Like humanity has only ever needed more energy and I don't see that changing. Right. The sources might diversify more and more, but energy as a whole is not going away and there's a million crazy interesting problems to solve and there's all kinds of crazy cool tech that no one really talks about, which is why DW exists. Um Wasn't there like the energy viper guy on Twitter? He he always he'll always show him people talk like we never actually replace an energy source. We may add more of another one, but we never like he'll show the drive I'm pretty sure like the graph is like we've never replaced, you know, an energy energy source ever. It's just we've just Here it was now, oh now we found oil. Mhm. We figured out nuclear a little bit, you know, like Right. Yeah, but it never like cuts into the other ones. Like it's just we need more, so Yeah. That's why we we preach energy addition, not transition because And using technology, I mean, let's make it cleaner, right? Like I thought I don't think anybody is against that, right? And I think that's the biggest misconception is like that everybody just wants to like walk around in oil base mud in their living room. Like that's not Nobody wants to do that. Stopping by the park to dump out some oil into the into the the pond. It's like most oil and gas people are hunters, environmentalists, like they go camp, they ride mountain bikes, like we spend a lot of time outside and it's Yes, we want it just as clean as everybody else. I also want to be able to drive to work reliably every day and have electricity when I come home and all of these joys that energy brings to the world. just insane. I mean, you think about the whole infrastructure cuz everything it relies I mean, like we're talking to my daughter about water treatment the other day and it's just like like the amount of energy it takes just to run a water Yeah, just that and we just turn the faucet and there's clean water and that it's just that all stems energy has a huge part in all that. All contingent upon dense energy. Yeah. Well, coming back circling this back to, you know, tech. Guess what? All those AI models run on GPUs and guess what GPUs need? A lot of a lot more energy than compute has needed historically ever in time. And so, even just just on the technology side, the energy demand is going to continue to grow and grow. Especially if we electrify everything. Yeah. That's the That's to me the biggest like misnomer. It's just it's frustrating to hear. It's like Well, it just comes out of the wall. Right. Yeah. Sparks the magic. That's what we called it in in college. The elec- the electrons are made with magic. [laughter] Okay. I think we've got about 5 more minutes to to wrap things up. So, we we typically end the episodes with uh some some uh the speed round. Just quick pepper you with some questions and get to get some good info out of you. Um so, I mean, you talked a lot about uh you know, that you like to have the support, but are there any open source, you know, tools that you generally like or have had a lot of success with? I haven't really used a lot of open source stuff. Now, be just because of the support, um a lot of things I've done, I need support cuz I don't have like we don't have a massive team. It's like me and another person basically, right? So, it's like you got to get it up and going and keep it maintainable. And so, um I don't really have any good open source. Yeah. Well, if you want me to just piggyback cuz I think it falls pretty well. Like, what's your favorite managed service then? Well, managed service uh I mean, again, I plug Microsoft Cloud like I work there. Um you know, Azure's the I think the the best inclusive cloud. You've got a lot of tools. So, you can get up and going with stuff very quickly. You can connect everything. And it's a good place to learn. Uh that's what I like. I want a product I can learn from. Um and so, yeah, definitely Microsoft Cloud. Nice. Yeah. What about uh language? What What do you normally if you're doing any code or Some Python. Um a lot of my stuff is like just small scripts. I don't write any huge libraries. Uh I mean, I can sling a lot of JSON. Yeah. [laughter] I can map I can map the hell out of some JSON, you know? gateway drug to data science is API calls. That's exactly how I feel. Yeah, so APIs, right? Like, that's what I've uh focused a ton of time on. I actually find that I'm a terrible front-end designer. I've designed a lot of front-end. It's not good. No, yeah. But it's functional. Design is difficult. And you had like the advertising background and where you even done some of that before. Right. And so, mine might look better than other people's bad designs, but it's not great. I really love back-end I love APIs. I'm just an API aficionado. I will go look for like I like the ISS International Space Station has an API that you can you know, like I just go find all these obscure APIs. Yeah. Yeah. I do the same thing. Yeah. I know. I see your LinkedIn posts and like, yeah. It's fun Well, it's just like, hey, I can type a few things and I've got all this data available to me to do whatever I want with. Exactly. And it it it's when it's when it works properly and it's well documented and if there's no issues, APIs are awesome. You know You know what's an amazing company like real quick and you I think you'd like it. You should probably talk to the guy Ethan who runs it. It's this company portable.io. And they're like we've talked about Five Tran before. They're like Five Tran, but they'll write it for free. any obscure API. Mm. Dude, I talked to him for 30 minutes and I told it was just like, here's two APIs. Like, it's not a big deal but if I get I swear when I got I got off the call with him he's like, here's a prototype. Like I don't know what system he has behind it. But he can connect like any API and have it into a like a snowflake data warehouse like it's freaking insane. Like he's got some system behind there like he connected to it like you just tell them like this is what I don't have I want it and then they'll build it and it's 200 bucks a month or whatever like Yeah. Oh, that's cool. Oh, that's real cool. Yeah, that's I think that's where we're starting I mean you mentioned it Fivetran. I've messed around with that a lot based off of Bobby's recommendation and it's it's it's kind of like Zapier but for APIs, right? It's you've got all these pre-built APIs. You just connect them, you authenticate with your credentials and then it you set it it gives you a little GUI that says how frequently do you want this to pull the data and then where do you want me to push it? Do you want me to push it to snowflake or big query or where do you where do you want me to push definitely will. It's Check it out for sure. They're pretty slick. Um but yeah, it's one of those things it's like yes, as a developer you could hire someone or do it yourself but then especially like this is my big issue that I run into with a lot of APIs because on the marketing side a lot of them are big public you know social media stuff and they're always updating them or changing the OAuth workflows or you know, they're always trying to get the latest security which is great but a huge pain in the ass if you're a solo developer solo tech data person trying to do this with all of a bunch of different sources, right? Because it's like okay, well I've got to go back and rewrite test it and figure it out or I could just pay someone a few hundred bucks a month to do all of that for me and just turn them on and off and That is very cool. It's yeah, it's it's pretty slick. Um do you have any uh favorite GitHub repos or Python uh Uh GitHub repos actually Noster. So Noster is a protocol. I I don't know if you're familiar with it but it's like a it's like a uh uh decentralized social network. It's run on lightning, right? Well, lightning's part of it. That's the payments part of it. But Noster you basically have different clients. Uh the one for iOS that I use is Damus. And um you can like import, so say you got kicked off of Damus, you could go to Blue Sky or another client, import your your key, like it's a a key that you have, and it'll like you could be anywhere on any platform. So there's no central governing body of it. And there's a ton of development going on. Lightning, which is, you know, layer two of Bitcoin, um is uh integrated with it. And so you could like pay people in Bitcoin for content. Uh I think it's amazing, and that's the repo I've been following. I've been trying to trying to figure it out. I'm learning web sockets to try to develop something on it. Yeah, so. Yeah. Yeah, now Noster's really really fascinating cuz it's it's a a you described it perfectly, decentralized social network, but the whole idea there is that you can't get banned cuz it's all your information. It's your private get [clears throat] banned from the client, but you can't get banned from the app. or to another client platform, Yeah. all your stuff is still there. And then that leads into the Web3 stuff of you own your data. And if people want your data, they can pay you for it. out to Brave browser, amazing browser. Yeah, it's a decentralized browser. Very cool. Um favorite or influential book? Okay, this is probably going to either make some people mad, but Elon Musk's new biography by Walter Isaacson. So Walter Isaacson has chronicled like Benjamin Franklin, Steve Jobs, like notable historic figures. And regardless of your opinions of Elon Musk, he's a prolific individual, whether you hate him or love him. The book's really well done. Um it shows you like how crazy he is from like personal relationship standpoint, but what it takes to like get some some monumental stuff done. And so on a microcosm, it's like made me look at what I'm doing and sort of like put it under the light of scrutiny in a healthy way, of course. Yeah. Uh but that's been Yeah, it's my I'm a real I try to get like two books in on Audible a month. Yeah. And so that's been my first month. to download it cuz when I did read Zero to One like it was it was Peter Thiel but it but it gave you like insight into that PayPal Mafia mindset. incredible. Yeah. Again, you need to go Zero to One. You need to like do something big and earth-shattering but like it explains why like for a while I was like Elon Musk is like a what would happen if you gave a billionaire or a five five-year-old a billion dollars. Right. to go to the moon and I want to build huge But he's doing it. But like [laughter] but he's doing it but then like you just understand like it could totally flop but like he wants to do something that's literally no one's done. Like Yeah. Um so But his new book doesn't just pump his stock. Like it definitely shows the human side which is helpful because I think that our generation has seen like the Facebooks and all these companies and there's like all this mythology. Yeah. And it made everybody feel like well what why didn't I create the Facebook or something like that and then you start seeing behind the scenes is helpful. Yeah. [clears throat] Absolutely. As we wrap up Yeah, just uh Yeah, I was going to ask like who's your uh favorite social media follow? Uh probably Sir Sleepy or Tangle on Noster for memes. Okay. really banging memes. And [laughter] we're all about the memes here at DW. Don't worry. Go no further. Uh and then ZeroHedge probably for like you know they're uh they're on Noster as well. Twitter Yeah, so ZeroHedge is probably Yeah, they have some really good stuff. Yeah. Yeah, I like uh yeah, as much as we [ __ ] on social media for all the terrible things that it does to society, having people like that on there, you know, that just put out really good interesting stuff is is such a good benefit but man, appreciate you coming. Where can uh where can people find you? LinkedIn. Yeah. And then uh I'm on Noster as Reboshi. Okay. It says like robot and Satoshi in my photo. Yeah, Reboshi. What about Aryan? Uh yeah, so Aryan.com. Um if also I'm looking to hire somebody who knows the Microsoft stack, uh uh doesn't have to have super big chops for from the ground-up coding, but like understand how to integrate APIs and I I got someone we need to talk after. Yeah. Cool. So, that's where you can find me. Yeah. Thanks for having me. Yeah, thanks, Jeff.