Virtual Machine = Real Collaboration

Speaker 0: Alright. Hi, everyone. Take a deep breath. Last presentation. Thanks for, staying strong Speaker 1: and sticking with us. My name is Ian, and I built Apple Retail's point of sale. I was glad that they check you out of this board. We deployed that globally on a Black Friday and transact 1000000000 dollars on day 1. I didn't sleep much at a time in my life. Speaker 1: I did a lot of work with Home Depot, Kroger. I was in gaming. I've done a lot of different things, so feel free to come up, chat with me, and those topics. I currently run a AI data consultancy called Sn Works, and we work with really big unstructured data problems with AI. In doing so and in building stuff, we came up with what I'm gonna share with you guys tonight. Speaker 1: So why are we here? Do any of you just you're the only coder. You don't work with any other coders. Show me your hands. Alright. Speaker 1: There's, like, 2 of you. So everyone else knows the real thing, which is where 2 or more are gathered, there will be problems. Right? And so we have all these tools where we can accelerate everything. This is open code. Speaker 1: It's similar to pod code or whatever else to use. Alright. But we know that you can all code the same ideas. You can even talk about it in meetings. And if if 5 people coded the same ticket, it would be 5 different ways. Speaker 1: Right? That's that's the struggle. You start compiling the stuff. You start putting the GitHub. Then you start to roll it out. Speaker 1: And pretty soon you're like, wait. Weren't we using functional programming? How do we get here? All of this is object programming going on, and all these problems start to compound. So as we saw that AI was accelerating what we did, we realized very rapidly that it was build local, push to GitHub, and then go, what the heck is all this? Speaker 1: And so we pulled back and said, well, can we fix this? What can we do? So what you see is not anything that's, like, super revolutionary, but what it is, I think, right now is a dark art. So if Speaker 0: you are even trying to play Speaker 1: with this, you'll you'll understand. Essentially, this is your imagined plot code, local, your empty file is what you do, except this lives on a virtual machine. And all of those files and rules are there on the virtual machine. And whether you go direct to a browser or the the app itself, or you can do it in our Discord. So we have various team members of various technical abilities can say, I found a bug doing x. Speaker 1: Fix it. And it will code it according to our rules, our structures, how we like to test things. You could have compliance, security rules, whatever you want. So it's not too different than some of the other presentations except it's all happening in real time in the builder, and it keeps everything looking and feeling like it's actually our product. So let me just walk you through a couple of the elements here. Speaker 1: First of all, I'm gonna come back to this. This alright. Shut down. Didn't it? Well, while it is spinning and blinking I spun up our dev environment. Speaker 1: There we go. I just wanna preview. This is you can see the URL. It's using the uninvited bot. That's the name of our bot. Speaker 1: So this is in the virtual machine. I just spun up our dev environment. I don't have to ask a developer to do it. They don't have to merge code, push anything, compile anything, publish anything. It's just ready to go. Speaker 1: I could say I want test data, and it would add test data. So I can, like, test out the product all my money. But I wanna come back to this. Sn what you see is that right now, the route status is any. Now there's obviously the data in there. Speaker 1: But that's that's gonna be important because we're gonna actually submit a ticket and you're gonna watch how this all happens because the the smartest idea in Dom is to do real work to show you guys how it doesn't work. But let me talk about some of the elements. So you've got agents. Right? Kind of at the top level, there's it's a file. Speaker 1: Right? It's empty files, got instructions. Where things start to get interesting is, like, when you get into Solution. How many of you have gotten caught in the go test this and fix it loop of doom? I won't make you raise your hands, but the other hand's going up. Speaker 1: Hey. I love to fix stuff. You tell people to fix stuff. You'll fix stuff forever. There's no problems. Speaker 1: They'll find problems. They'll just, like, keep fixing them and fixing them. And you'll just spend that money and it's like, man, this was crack code. You're like, but wait. It's getting worse. Speaker 1: That's impossible. So, I know it's a little hard to see and I think, like, a few minutes time because the screen compressed a lot. But we have a type check, a test suite, local rules, reviews, testing. We segment this out. It has very specifics of type checking. Speaker 1: Maybe you work in TypeScript. If you just send the l m to go check it, you'll get crap type checks. Like, it's still got type errors even though it wouldn't check it. So this is like 1 of those deterministic tests. This is how you check type. Speaker 1: There's CLI thing you do. It's only that you are the agent. You're just checking to make sure the type is clean. Right? That saves so much time and effort. Speaker 1: Trust me. Go do this today. Like, do it tonight. But what you can do is you can have all these things uploaded, and there can be Real. This is the prompt for that 1. Speaker 1: We've got, you know, the different tests. They all break out. So, again, I'm not gonna go super deep into all that, but I just wanna show you that all this stuff can be loaded in there. This is the hard part. This is where you have to spend time with your team. Speaker 1: You have to iterate. You have to try. You're gonna run tests, and they're not gonna work right. You can come back and refine that. But this has really revolutionized the way we code, how we do stuff. Speaker 1: So what I'm gonna do is go in here. This is a very small feature. Our customers want or they showed you that tab on that 1 Real. They want it to be preset to only active routes. That's the default. Speaker 1: Right? It's kinda dumb. Pretty simple. I have acceptance criteria. Obviously, our system is already connected into Notion where we keep our tickets. Speaker 1: But I just wanna show you as I push it in, and I'm not cheating. Sn we're gonna send that Works, and what you're gonna start to see is it's gonna understand what Works is. It's gonna go look in. It's looking where that is is situated in code. But the important part is as that's happening, I'll also bring up I can I can force it to do the check, so I can send it into that test One string? Speaker 1: It's gonna go through on its own. Sometimes it even finds bugs. We have rules within our testing on how to then, you know, find, fix a bug One just go ahead and do it. You may say, I don't want that to happen. If you're running 57 different agents, maybe just let them do it. Speaker 1: Right? It all depends on your level of confidence in what you're doing. Sn this is actually building out this feature. As it's running, it's gonna code it, submit it. I can then push it into dev, which will probably happen while we're asking questions in the space that it is running. Speaker 1: And then we will relaunch that dev view and you will see the feature sitting there. So this is kind of like, again, simple, but it took a lot of work behind the scenes. And what it's enabling is someone can QA test something super easy that I like the product manager can spin something out in a whole environment One then just go put test data in. Right? Imagine how much time we've all spent doing those exact tasks. Speaker 1: But it's the code on the other side. Like, we're very particular. We like everything componentized. We like TypeScript. We like effect with TypeScript. Speaker 1: If you just told an LN to code this stuff, you you get, like, an HTML app. Like, where did this come from? You know, like, there's no rules and structures. So this is all about that kind of underlying rules. Alright? Speaker 1: I've changed the file. I've ran Solution. And so what I'm gonna do is I'm actually gonna just turn the dev down. We're gonna shut down the dev environment, And then we're gonna relaunch it. But also Agent to show you how easy it is to kill and relaunch an environment. Speaker 1: So having this in the virtual server, you're not, again, building all this stuff. But One, anywhere, if you give them, Tailscale VPN access, it can do this. No 1 else gets access. Right? So it is secured. Speaker 1: It is structured. And you can ask me questions about all the the surroundings. Alright. So we stop the back end. I'm gonna relaunch Data, and then you guys some of your questions, and I'll bring this up in a sec. Speaker 1: Anybody questions so far? We're Speaker 0: we're gonna, We're gonna have to leave the the questions for the back burner, I think, just so we can finish out. This is a little demo. Is this is this running Speaker 1: in the cloud, or is it running, like, where where This is this is running on GCP Yeah. On a virtual server. Okay. Here we go. Okay. Speaker 1: I've actually clicked this with TelScale, so, that's obviously important. Servers are spinning up still, so it'll take a sec. Here's that route planning screen. It looked active. That was not there. Speaker 0: Hey. 1 per chain. Speaker 1: So, yeah, you can you can always sit anywhere. You know, we we have some free server time on GCP. So today, we also have that on Azure. We work in both. But, yeah, I I definitely recommend trying moving your stuff in the cloud. Speaker 1: My open calls in the cloud. Like, why are you waiting around for a man behinds? I'm too much money. I'm just gonna get my hands for free. Who's using the custom Speaker 0: code here right now? 12345. Cool. Yeah. This is a brilliant, Speaker 1: kind of demonstration of how you folk clove, open, Speaker 0: and having, like, a whole DM that spin off. They're all spin off. It's really interesting. So I'm sorry. I we are a little tight on time, and we wanna make sure we got a little time out back. Speaker 0: So what I would suggest is, like, just jumping on top of Andy as soon as he walks down the aisle and ask him a ton of questions. Speaker 1: The Speaker 0: last thing we would be