Is that, is that kind of how some of how this has changed where, where you would take a week to program something, now you're doing, you know, an hour or two kind of planning, building upfront, and then some time on the back end? Or tell us a little bit more about how you're incorporating this in, in your coding.

Yeah.

It might be useful to kind of give you a picture of, of how development normally goes.

And so it depends on what kind of application you're building and how rigorous you wanna be.

If you're just coding up something for fun, you know, that's a lot different than developing production software.

Um, so a lot of times, um- Software houses will have their guys write tests first.

So you write a bunch of tests of how you want your software to operate.

So that, that's where I would just tell people to look is look at those areas.

I mean, I could go on and on, but

Yeah, so in the software world, what people are doing now basically is you have experts who can code well themselves, but working with agents, they're essentially able to have an army of junior level programmers that they can send out to then build a bunch of stuff for them.

And they can be sort of like the skeptical eye that does the review process.

They say, well, we actually need to do this and not this.

You're basically becoming like a manager of multiple other programmers, right? So in the coding, to use the coding analogy world, we're able to sort of multiply effort.

And coding is one of those few applications that's extremely relevant and the models can do really well already.

There's a guy, one of the, I can't remember which one he works at, but Andrew Carpathy, he's the guy who came up with the vibe coding definition or whatever.

I think it's really complex, actually.