@darrenshawseo

Like how do you feel about vibe coding then and then launching those tools that people can pay for? Do you think like this is kind of the future of like a agency to Sass or like new Sass products? Yeah, I would say one of the things that agencies can definitely start exploring is vibe coding their own little tool for this little efficiency hack for that.

Like they can vibe code individual tools and Chrome extensions and that kind of thing.

It does a decent job and it's like just don't look under the hood at that coat cause it is trash. It's like absolute garbage coat inefficient, doesn't scale all kinds of problems. So yes, I have already vibe coded a few things.

You can find them on the website.

I did the freshness distance calculator. I made this cool little tool that I will show. It just basically scrapes the Google results, tells you like, you know, this was published 3 months ago, two days ago.

And then based on that, it calculates how often you should be updating your.

It's a free tool and we can go and use and it does one task pretty well. You could never in a million years vibe code a piece of software as complicated as our new local ranking grids. You can make a real piece of version of it, but you can't make an ultimate like this is a like an actual industry leading piece of software.

You can build a little side thing that does one task well.

And specifically if you're going to use it for internal stuff. I love it. Go ahead.

I use cursor actually.

And I'll tell you one thing. If you're going to vibe code, I'll give you a little tip. Your your vibe coding should be a week of just working with ChatGPT.

Going back on the requirements document, you want to have a really very well detailed this is what the application does.

These are the APIs that uses this is how it does this thing. This is what I want the user flow to be. You just like describe the application in such excruciating detail.

And then you give that to the to the I use cursor and I'll just give it to that.

And then there's a document that the cursor keeps referencing. And so we just kind of step through it as we build the DOC as we build the application. So anyways, that's those are my thoughts.