What is vibe coding?

- So I want to debunk a little bit of a myth around vibe coding. Oftentimes when you research this or look it up, you'll see people discuss vibe coding as it's something that you completely outsource to AI. But in this video, I'm going to walk you through the importance of adding structure to the vibes. Vibe coding. So what is vibe coding? Well, oftentimes when you hear about vibe coding, I think about it as a spectrum. So on one side, on the left hand side, we have less vibes, and on the right hand side, we have more vibes. Depending on the person you're speaking with, the definition changes. So for more vibes, it could be somebody that heavily relies on the AI, and then on the left hand side, for less vibes, that means that you have fewer reliance in the AI, assuming that you're likely somebody that's more technical. And there is no right or wrong answer here. It's just the type of person and experience you have prior to coming to the AI to use it for assistance in writing code. Another thing to point out is that with AI, it increases in its intelligence over time. And as AI becomes more effective and capable of achieving more complex tasks, that means that you can rely more on the vibes and less on structure. But today, as of now, it's important to have more structure to your vibe coding process so you can build more effective applications, faster without many errors. And that's exactly what we're going to talk about today, adding structure to your vibe coding process, and showing you hands-on how to apply that structure to building application together. And here's the good depiction of how I visualize this. So in the vertical axis, we have complexity. On the horizontal axis, we have structure. So the more complex the application gets, the more structure you would likely want to have, so you can then in turn, provide more value to either your clients, your employer, et cetera, when you're building applications, automations for different purposes. So think more structure, the higher chances that you'll build something more complex, which in turn will be more valuable. One last thing I want to say here is with AI, oftentimes when you're building out an application, it starts to go off the rails if you have a long running conversation without refreshing it. So the name of the game when building with AI is context engineering or orchestrating the AI in an effective way. And the way we're going to do this is by having a series of documents that act as a vision for the AI. And as the AI builds, which is the arrow going down into the building section, we're going to reorient the AI on the vision over and over as we continue to build this application. So you can think of it as a cycle. So we start with the vision. We let the AI know where we are in the process. We start to build. After we built a bit, we reorient it again on the vision and come back to build. So it's a cycle. We're always trying to guide and keep the AI on the right track so it doesn't go off and make a bunch of bugs, errors, et cetera. Now that we have a good understanding of structure associated to vibes, let's walk through what that actually looks like with three special documents.