Beth Lyons

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.

I don't care what tool you use.

I don't think one is better than the other in that sense.

And how do they interact?

Where do they live?

I just don't think you turn the faucet on and go, everybody go hog wild and build a solution for yourself.

Because...

Honestly, a skill is still a markdown file.

It's the same damn thing I was doing with custom GPTs two years ago.

I was just saying that to a co-worker this morning.

I was like, a skill is not a magical piece of anything.

But social media will have you believe a skill somehow is some new magical AI solution.

And it's not.