This course is nearing its completion. And before we go, I wanted to share with you some tools and resources that I use outside of Cursor. Most of the course has been dedicated to Cursor and how I use that to build Wonder, but there are a lot of other things that I think you'll find helpful. So we know that I use Next Js and TypeScript. We've talked about my general stack, we've talked about V zero

We've talked about my general stack, we've talked about V zero and how I use that for prototyping. While I'm bragging on Versal, I really like the ai SDK, it's just a really easy, nice way to switch between models and build your application in a way that makes switching easy. It doesn't matter if you use the AI SDK from for sale or some other provider's way of doing this. My thing that I really, really want you to do is make sure

or some other provider's way of doing this. My thing that I really, really want you to do is make sure that if you are building an AI powered application, that you are not model dependent. That you build it in such a way that you can go in, uh, whether you as the owner or the user, or both can change the models. These things are changing every day. They go down all the time. One is better than the other,

They go down all the time. One is better than the other, and then something changes and another is better. You need to build in a way that you are not dependent on any one model that you can switch back and forth between who's ever winning at the moment or whoever is more reliable. To that end, I also use Grok for some of the cheaper inference tasks.

To that end, I also use Grok for some of the cheaper inference tasks. You don't need to use a large super huge late state-of-the-art model for everything. I have had a lot of trouble getting the open source models to do the things that I want them to do at scale, like the big cool stuff that you wanna do, but very small tasks. I don't know, maybe you wanna auto name something. Uh, things like that. These small models are super cheap

I don't know, maybe you wanna auto name something. Uh, things like that. These small models are super cheap and Grok serves them super fast. So that's Grok with a Q, not Grok with a K from XAI, grok with a Q has super fast. Uh, really cheap models that you can use, uh, for next to nothing. Honestly. Really great service, really reliable. I really like it. Super base. I am all in on superb base. I cannot say enough. I'm just like every other Vibe coder.

I really like it. Super base. I am all in on superb base. I cannot say enough. I'm just like every other Vibe coder. Superb Base is a great product. Um, I use my, the authentication through there. I'm using Super Base storage. I'm using superb base real time. If we went back to Winder, if I drag these around, you can see that it's moving very, uh, Figma like experience that I have real time. That was so easy. I dreaded implementing that.

that I have real time. That was so easy. I dreaded implementing that. And then when I did it with Superb Base, it was just so easy. Took me an afternoon or something like that. So, uh, superb base is absolutely incredible. We have not talked at all about security, um, in this course. And I just wanna take a second to say one, use superb base if you don't know what you're doing.

And I just wanna take a second to say one, use superb base if you don't know what you're doing. If, if you absolutely are a backend engineer and you know better and, and how to build your own backend or use a different service, absolutely. If you don't know what you're doing, if you are not a backend engineer, use a product like Superb Base that's fairly secure out of the box. But you have to have to have to learn about security.

that's fairly secure out of the box. But you have to have to have to learn about security. Uh, it would, uh, you need a whole course on that. That is not something that you can shortcut. It is not something you can vibe. It is not something that you can prompt. Security comes from knowledge. And you as the, the owner of a platform that stores user user data, you have absolutely no excuse not to beef up your security

that stores user user data, you have absolutely no excuse not to beef up your security to have a a non-secure platform. That is the thing that vibe coders are getting in trouble for. You see security breach after security breach after security breach. You are responsible for other people's data. And if you do not understand basic database security, then you should not hold people's data

And if you do not understand basic database security, then you should not hold people's data that is just full stop. I am not a Vibe coder that says you can do it all on your own without ever being technical. I just do not believe that. You need to know and understand database security. You need to watch all of super basis videos. If you're using it. You need to read their docs.

You need to watch all of super basis videos. If you're using it. You need to read their docs. If you don't understand what row level security is from day one, don't vibe code, stop at least, uh, for anything that holds actual user data. You can absolutely vibe code for your own little products that live on your computer and are not in the cloud. But the second you wanna put someone else's data onto your platform, you need to learn about security. And there are no shortcuts.

platform, you need to learn about security. And there are no shortcuts. There are no ways to to go around this. Uh, learn row level security, learn column level security. Learn how to secure your endpoints. Have an engineer friend. If you are not a professional backend engineer, have an engineer friend. Try to poke around your end points. See if they can get data out of them, because odds are, if you're vibe coding something,

See if they can get data out of them, because odds are, if you're vibe coding something, then it's a mess with security. These things do not by default create secure applications and you need to do everything you can to do that. I personally don't let Cursor touch my database. So my, I have a firewall or just a gap I guess between Cursor and Superb Base where all the time, superb base or a cursor wants to do things.

and Superb Base where all the time, superb base or a cursor wants to do things. The models that I have in there, they wanna do things like drop all my tables, erase all my data. I've seen so many stories of this online. Do not, if you don't know what you're doing and, and, uh, you don't fully trust the model, it's like I don't let the model do things. In your live production database, you can set up a sort

it's like I don't let the model do things. In your live production database, you can set up a sort of mirrored database that doesn't have production data in it in sase, and you can just air gap it so that it, that can't actually run, uh, SQL on your, your production database. Just don't let it because it, it'll erase your database and that's not good. So make sure you do that. Also, make sure you use gi I see Vibe coders, uh, say

So make sure you do that. Also, make sure you use gi I see Vibe coders, uh, say that they lost two months of work or something like that because they're not using GitHub. That's no, just don't, don't do that. Use Git that you should never lose more than 20 minutes of work or something like that. You gotta learn Git. I'm sorry. It's just, if you're a vibe coder and you don't know it, just stop.

It's just, if you're a vibe coder and you don't know it, just stop. Learn database security. Learn, get, there's no way around it. Next up Codex, I would like to do potentially a whole course on Codex. I don't have time to get into this right now. It is very different. And so if I jump over to Cursor, you can see that I have been using it.

And so if I jump over to Cursor, you can see that I have been using it. Codex, uh, started life as a CLI tool, like cloud code. Now there's a really nice integration with Cursor, so I've been using that a lot. Um, it feels and looks like Cursor inside of Cursor and, but it's from OpenAI. It's very confusing. Um, but it turns out that it's not hype. I thought it was hype. I avoided it for a long time.

but it turns out that it's not hype. I thought it was hype. I avoided it for a long time. I was like, I'm just so exhausted. I don't wanna learn something else. Do you wanna learn more stuff? It's just I'm exhausted, but it turns out I'm sorry, it's not hype. It's really good. There is some magic in here that OpenAI is doing. Uh, they recommend I've looked, uh, at some of their docs

There is some magic in here that OpenAI is doing. Uh, they recommend I've looked, uh, at some of their docs and what their folks are saying online. They recommend that you leave it on medium. But uh, basically you have, uh, a very specific model that they've released for this. Now. It's not just G PT five, the model itself is GPT five Codex, which you can also use in Cursor. This stuff is so confusing.

which you can also use in Cursor. This stuff is so confusing. Um, but uh, it's different inside of this Codex plugin itself, which is as far as I understand the same as the CLI experience. Um, just with a different ui. The thing that it does more, it seems to be a lot slower in a good way. It thinks a lot, it chews through a ton of context, but remember the the context rot principle

It thinks a lot, it chews through a ton of context, but remember the the context rot principle that the more context you chew through, the worse it gets. I would say in my own non-scientific way of experimenting that the context rot is much less of a problem in Codex. That is the best thing I can say about it so far in that I have been giving it things that I cannot get done in Cursor that I've been banging my head against the Wall cursor agent.

that I've been banging my head against the Wall cursor agent. Even with GPT five, I just can't get it to work. I give it to Codex and I one shot it and it's working. I am really impressed with this product. Um, and I don't know what the future holds for me and using any product but this because it's so good. I hope that, you know, other platforms catch up and that cursor catches up and vs. Code catches up and, but for right now,

and that cursor catches up and vs. Code catches up and, but for right now, codex is really impressive and even though I've done this course just mostly in Cursor, you should try Codex inside of Cursor in the CLI, you should absolutely try this product. It's really impressive and I know Claude code is potentially just as good. I haven't been using it a lot, but I know a lot of people swear by cloud code as well.

I haven't been using it a lot, but I know a lot of people swear by cloud code as well. So these CLI tools, there's something there. Um, they have, they have access to the models in a sort of closer way than these third party providers, which is maybe good, maybe bad. Um, but uh, for you as a Vibe coder, it really is an impressive experience. Resend for emails. Um, there are a lot of email providers. I haven't tried them all, so

Resend for emails. Um, there are a lot of email providers. I haven't tried them all, so I'm just telling you what I use. It was really easy to get set up with recent, uh, there was nothing there in terms of some of the front end stuff that I use. Lucid icons, I think this is fairly common in the vibe coding world. Uh, just ton of free icons. It's great. Uh, I've also been using Daisy ui.

Uh, just ton of free icons. It's great. Uh, I've also been using Daisy ui. I didn't want everything that I did to look like Shadian absolutely great, uh, sort of, uh, component library, but Daisy ui uh, is just has a different vibe and I really like it. And I think the, the developer here has been doing really great work. Alright, so that's a lot of stuff, but those are some of the, uh, resources that I use

Alright, so that's a lot of stuff, but those are some of the, uh, resources that I use to build winder, um, some of the resources that I use to build other projects. Uh, it's super useful to try some of these tools. Lemme know what you think of them. All right, we'll see you in the next one.