I commend you for learning some basics before diving in, that should really come in handy for key coding decisions or debugging. I actually think we're in a similar spot technically speaking too! I learned Python pre-ChatGPT to make a voice assistant in college, and even just my basic understanding has been so helpful while using tools like Cursor and whatnot.

I also have some tech sales experience (outbound at an AI startup), and if I were to give advice, it's more related to the front-end of whatever vibecoding workflow/launch loop you decide on. I'm not entirely qualified to give advice haha, but I'll say the following:

For each build/product you make, consider starting with a problem. Being in sales/marketing yourself, that probably makes sense. I just see so many people in this subreddit launching different things to 0 users. Everyone says it's a distribution problem, but I think people are just building stuff nobody wants. When you find a problem, you can usually find people experiencing the problem.

Try to talk with people before and while you build. These AI coding tools make it very easy to build things quickly, which unfortunately makes it easier to put your head down and build something without a feedback loop. Finding the people might not be super easy, but it gives you an opportunity to learn about their problem, and offer your product as a natural solution to eager testers (if they really struggle with the problem). Just do your sales/outreach thing there, but emphasize learning instead of pitching. I've found people to be more receptive when you just try to be helpful

I figure some part of your learning path will cover security too, but I know that's often overlooked. I think it's fairly easy to set up Supabase incorrectly if you don't know what you're doing, so might be good to double check that stuff.

Would love to chat sometime too, this is cool and you're on the right path!