Beth Lyons

This is even something internally with scale, but I'm seeing it with my clients too.

Here's my fear, truthfully, is that it's great that everybody has this tool and they go, oh my God, I can build solutions for myself that make my job easier or whatever.

And they might be internally facing, they could be client facing.

But there's a lot with these tools, I think, that are going to be more internally facing.

especially since it's local files.

I mean, yes, there's GitHub and stuff, but again, you have to go back to who understands how to use it, who's going to maintain it.

It doesn't just magically happen by itself.

People can overwrite stuff.

You got to be careful, right?

So when I look at it, what my biggest fear right now is that people, if left to the wild,

The team would just build all sorts of solutions that would be so different because cloud code or codex or anti-gravity is going to take its pattern to build it.

And it's not that it won't be a usable solution, but I do worry that we're going to get six months down the road.

There's going to be 30...

apps that we self-host for let's say scaled or a client or whatever and we're gonna go do they work yeah they all work and then you're gonna go who who's gonna fix that when it breaks who's gonna who's gonna and like what is the modeling or the prompting behind it now the answer could always be

I will just ask clog code what the prompting is and I will fix it from clog code.

Why would I need to know what the prompting is if it works?

And there's there's some truth to that.

But I think we're it's a scary proposition to jump from to your point and about like maybe using the terminal or understanding how it all sort of pieces together in a more raw format.

That is helpful if you're building systems, whether it's for yourself, your team, or externally for clients.

Because I think it's a scary scaffolding problem to have all these built code solutions.