Vibecoding should use AI as a tool, but not trust it blindly - here’s 4 ways I make sure I’m building responsibly 💁🏼‍♀️ #vibecoding #nocode #learnwithme #aiapps

Let's talk about how to vibe code responsibly. So what do I mean by that? First of all, you need to know as you start your project what you're actually building. And I don't just mean I'm building an app or I'm building a website. You need to know how it will be built and how it will be written. So put in a little bit of effort upfront to learn about the different languages and what is best for your use case. You can still use AI to do this. Talk to chat GPT, talk to Claude, say, hey, my end goal is an app that I wanna have on an iOS phone and I wanna be able to put it in the Apple App Store. What should I be building? It will tell you, and then you can use that to prompt whatever tool you're using to actually build for you correctly right from the beginning. Next, building on this, you need to be able to read what this has actually written for you. So it's super important to me that I'm able to download my code or view it in a code editor just so that I'm aware of how it's written things, how I can access something if there's a problem. I can pull pieces out of that to give it to chat GPT or to review manually. But just, again, putting in maybe the half hour to one hour upfront to learn how this has been written, how I can read the actual backend files is going to help you so much in the long run rather than just relying on this black box of a bolt.com or something similar that's holding all of your code and you have no idea what's going on. Say that there's one caveat here. If you're dealing with any sort of sensitive data, you definitely need to understand fully the ins and outs of how you are storing that data and how you have coded for that data in the code. Because if you don't, you could be exposing that and it might be potentially sensitive. So that is something that you need to take super seriously and be 100% sure you know what you're doing or get somebody who does to help you out with that piece. Lastly, you need to put in the work for testing. And I don't just mean testing it on Expo Go on your phone as you're building it. Of course, you have to do that to be able to build the app. I mean, once that's done and you've published your app or you have your final version, put it into TestFlight, have friends test the app for you, test it on different screen sizes, try to break it, try to go through different user flows that maybe you hadn't thought of, test it over time if you have anything that's depending on like a day changing or time zone shifting, anything like that, just spend the time to actually go through and test it rather than just spending an hour talking to an LLM and then saying, oh, I have an app that's fully ready to be deployed. If you get to the point that you're doing all of these things, essentially you are just building an app. The only part that is vibe coding is the actual writing of the monotonous code that's being done for you by AI. That's like using a calculator to do math. That is just smart. That is what I would expect somebody who has the technical experience to write that code should be doing as well. We're all just skipping the hard stuff here and moving on to the pieces that are more important for user flow, for testing, and building something that is actually helpful rather than just something that's meeting technical requirements that were laid out weeks ago and have since changed.