Beth Lyons

By the way, they're saying in the comments too, it's a big story.

I'm saying if it's a terminal story, it's a code and code work story.

Across the board.

That's all I'm saying.

A valid point.

I mean, what I would tell people is careful how much you let be, um, under behind a locked door.

Let's just say it that way.

Um,

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.