Ep 859: The Vibe Coding Boom: Why Vibe Coding isn't Going Away and How it's Both Good and Bad (Start Here Series Ep 18)

Welcome to the Everyday AI Podcast. My name is Jordan Wilson, and for the past 3 and a half years, we've put out more than 800 episodes. Yet one of the most common questions I get, I didn't really have an answer for. Where do I start on the Everyday AI Podcast? And that's why we started the Start Here series. And with fall now back in full swing, the Everyday AI Podcast is going back to school and playing back the entire Start Here series. From front to back. We've hit pause on our normal Monday to Friday programming to run back our most popular series ever for the next 30 days. We made the Start Here series for beginners and AI champions alike. So whether you're just trying to get a grasp on large language models or grappling with the best coding harness for multi-agentic workflows, the Start Here series covers it all. Plain language, no jargon, and easy to follow along each day. So make sure to subscribe to the podcast and check back each day for new insights, day by day. The series is a culmination of spending more than 10,000 hours covering generative AI over the past 3 and a half years. So you don't want to miss a single episode of the Start Here series. Let's get into it.

Imagine that you can describe your dream house out loud and poof, a building appears in front of your eyes in minutes. It looks incredible. It's exactly what you asked for and you move in. It's awesome. You tell everyone how easy it was, but then almost instantly you want to make some changes. You want to add a second floor. Heck, maybe even an outlet here or there, or just maybe you want to hang a towel rack, but then you run into some problems instantly. You realize that no one knows which walls are load-bearing or if the electricity works. And turns out that those floors look sturdy, but when you plopped your couch down on those marble looking floors. Turned out that they were kind of paper thin and they started to sink. And it turns out the whole structure was great in theory, but it was held together with duct tape, hopes and dreams, and there definitely wasn't a permit. And now you're in trouble. And this scenario is exactly what's happening right now across the enterprise and the software industry at a scale that we haven't seen before because of vibe coding. But is all vibe coding bad? Is it all smoke and mirrors and hallucinated code that's held together by strong models and agentic loops? Or can you actually vibe code a production-ready app without much coding knowledge? Today we're going to be giving you those answers and breaking down the vibe coding boom, the opportunity, the potential crisis, and why none of this is going away. All right, let's jump into it. Here is the big picture of what we're going to be covering. on today's show. Because you can't escape the reality right now that AI has completely collapsed the cost of building software. But it's not all good. Right now, it's estimated that about 41 to 46% of all new code written globally is now generated by AI. And right now, uh, the latest update that we've seen, which is actually a pretty old one, is that 92% of US developers use AI coding tools at work every single day. But even Andrej Karpathy, who coined the term vibe coding, has now declared it passé after only one year. It's because we realize that it's not always all good. So on today's show, here's what we're gonna be diving into and what you'll learn if you stick with us for the next 20-ish minutes. You'll learn the top 10 vibe coding platforms that you should be paying attention to and their main benefits. You're gonna learn what happens inside AI-built applications at the 90-day mark that triggers billion-dollar rebuilds, and You're gonna know the specific strategies that separate vibe coding winners from the casualties. Let's get into it. Welcome to Everyday AI and our Start Here series. Yeah, after 700+ episodes, I legit had no answer when new listeners would come in and be like, Jordan, you have a lot of podcasts. Where do I start? Well, you start here, preferably in order, but the Start Here series is the essential podcast series to both learn the AI basics and to double down on your AI knowledge. So if that's what you're trying to do, Make sure to go to starthearseries.com. That's going to give you exclusive free access to our inner circle community. It's the only way that you can get in right now, and that's gonna plop you right in the middle of our Start Here series space there. And you can go back, read, watch, and listen every single episode in order, all the way from volume 1 to today's episode, volume 18. And if you missed our last episode, like I said, it's best if you listen to them all in order. And Volume 17, we talked about the responsible AI playbook and what it means and 5 moves to ensure your AI strategy survives. And that leads us straight to today because if I'm being honest, one of the things that when you talk about AI strategies, so many enterprises' new AI strategy is essentially vibe coding, right? Whether it's creating software for themselves or for their consumers or just vibe coding completely new ways to work internally, it's pretty easy So if you are like, wait, can you hit rewind here, Jordan? I'm brand new. I got you. Like, vibe coding is this. You describe something in plain English or whatever language that you speak, and an AI builds software, right? So it handles all the database, the deployment, the coding, even certain platforms handle the authentication, payment platforms, all of that, right? So This is a term that OpenAI co-founder Andrej Karpathy coined in February 2025, which is crazy to think about 'cause it seems like we've been talking about vibe coding for like 5 years, but it's been like 15 months, right? And I kind of called this out a month before, you know, kind of the vibe coding terminology even existed in our 2025 AI Predictions and Roadmap series. And I talked about at the time that non-technical people would be building themselves software by the year end. And I think that definitely came to fruition, but— Now fast forward into 2026 and the vibe coding platform has exploded in the scene and there's a handful of even different types or categories of vibe coding. And like I said, this is an exploding sector. So, you know, as an example, Cursor, right, they're an AI-powered code editor and they've already hit $2 billion annual recurring revenue in just a few months after, you know, their last earnings report. But most of the people fueling all of this growth are not even software engineers as well, uh, or at all. Uh, so yes, you can have traditional software engineers or developers who are vibe coding, and you've seen this as well, you know, some, uh, interesting but kind of, uh, I don't know if heart-wrenching is the right word, right? But talking, you know, reading these articles about, you know, software engineers with 20+ years of experience and they're like, Wait, these AI platforms do all of this now at a much higher level, better than I ever can, right? So it's almost gotten to the point now where, you know, if people know what they're doing, a lot of times experienced software developers aren't even writing code anymore, right? If you look at Anthropic, which you could say is potentially the leading software dev agency in the world, right? Because their products, Claude Code, Claude Cowork, are some of the best out there, right? they said they don't even write code anymore themselves. So first, before we get into kind of the good, the bad, the ugly, and why I don't think vibe coding is going away, let's very quickly, now that you have a basic definition of vibe coding, I wanna talk about some of the 10 maybe of the most popular kind of vibe coding tools. And they are in different kind of categories. And these categories, well, I define them. There's no exact definitions that the industry adheres to. And there's definitely a lot of crossover and, You know, you can make a lot of arguments, but I'm trying to simplify it for our audience that's beginning. So first, I'll say that we have the terminal or command line coding agents. So if you don't know what a terminal is, computers have a terminal and you can control your computer through the terminal, right? And it's becoming more and more impactful now as we see, you know, platforms very popular like Claude Cowork that you can literally run things on your terminal, right? So As an example, I always tell people, oh, I always have, you know, Codex and Claude Cowork running, and people are like, tell me what you have doing, right? So as an example, I have Claude Code going right now. It's going through my 750+ transcripts, and I'm thinking about starting a new kind of episode series where I piece together multiple interviews that I've done. I've interviewed hundreds of people over the years, and I've always thought, man, it'd be cool to kind of combine, you know, have 3 different people, older interviews, splice 'em together. You know, I can go in there and, you know, narrate between. So I have Claude Cowork, as an example, going through all of those local files on my computer right now, doing some research for me at the same time and putting together some ideas that I'm gonna go through and, you know, work with. So that's an example of a vibe coding platform, right? Claude Code, Claude Cowork using the terminal. So it runs in your terminal. It can read your whole codebase and make autonomous multi-file changes. And this is also important to talk about before we get into these categories and the 10 most popular apps is it's not just for coders. It's not just for software development, right? And I think that we'll start to see this probably in the second half or the very end of 2026. And I think it's not really gonna become apparent until we get the new super app from ChatGPT where they're essentially gonna be combining ChatGPT, their browser, and Codex. Because I've been saying Codex is not really, well, it is a coding platform, but it's so much more than that. So keep this in mind as we go through these, even if you're not a software developer, a coder, right? I think it's important to pay attention not just to the rest of this episode, but to these 10 different kind of platforms as well. So first, Claude Code, I'd say it's probably the most popular and one of the most widely used kind of vibe coding platforms. Although yes, it is much more than traditional vibe coding. So there's a lot of great new features that have been added. And again, depending on when you're listening to this, you know, so if you're listening to this in, December 2026, you know, some of these new features aren't going to be very new, right? But if you're listening in April, right, things like computer use, auto mode, Claude, or sorry, cloud, autofix for PRs, a lot of new things that have been released in Claude Code. And I think this is kind of the terminal agent that just reads and rewrites your entire codebase, right? The other thing that I've liked recently is the new 1 million context window by default in Claude Code. So by far, it is broadly considered the current leader in agentic coding quality. And code-based reasoning. But our second on the list here is catching up. So OpenAI's Codex, you know, they recently announced that they have 2 million weekly active users in Codex, which is pretty impressive for a product that's only been out for like less than 2 months, at least the desktop version. So this is kind of your multi-service, multi-surface agent system across the app command line, the IDE, and the web. So you can use, you know, Codex in a lot of different places. And kind of what's new or what's worth it is Well, the model GPT-5.4, I'm always in Codex using extra high reasoning. Yes, it takes a little bit longer, but in my opinion, right, if I'm running the exact same task in Claude Code versus Codex, Claude Code is going to be way faster and it's going to look way better. But usually Codex is going to have way fewer issues. Right. And that's the thing, too, with these coding, vibe coding platforms, you can work a lot of them in tandem, right? When I'm working, I usually have Claude Code and Codex working on the same thing, not at the same time. You know, I may have one with kind of read-only audit access passing things over to the Builder agents. But Codex, like I said, the desktop app just launched in February, and one of the cool things that they've announced recently is the ability to run multiple subagents in parallel. All right, there's a lot of other that might fit in that category of the terminal or command line interface coding agents, but I'd say those are the 2 big ones. Now let's move on to the AI native code editors. So these are essentially full editors that are rebuilt around your AI. So these are for developers, probably a little bit more than even Claude Code and Codex, who want AI inside of their existing workflow. So the big one here probably is Cursor. And this is kind of an AI-first VS fork code with background agents and multimodal support. That's the big thing right there, right? Multimodal support. Whereas obviously, you know, Codex by OpenAI and Claude Code by Anthropic run those respective models. So like I mentioned, Cursor did hit $2 billion ARR in February of this year with over 1 million paying customers. And then you can use the best models, right? So you can use OpenAI's GPT-5.4, you can use Claude Opus 4.6, Gemini 3.1, or Cursor's own Composer model. Next, Windsurf. So Windsurf went through kind of a weird middle of 2025. There's a bunch of these rumors, right? Oh, who's gonna, you know, who's gonna acquire them. You know, OpenAI was gonna acquire them, but then they didn't. But then Google essentially acquihired their CEO and some of their co-founders, and then Cognition acquired the rest of the company. But it is a great agentic IDE, right? And right now, that wild $2.4 billion acquisition saga. And sorry, I maybe skipped over a couple of definitions. I don't wanna leave you all here with alphabet soup, especially in our start here. Series. But what I'm talking about, you know, I already defined vibe coding, you know, command line interface, CLI, right? So that's essentially interacting with a vibe coding tool through a terminal, kind of a different way to use the terminal. And then when I say an IDE, that's an integrated development environment. So that's essentially like a toolbox for writing computer software, right? So it's a single application that combines all the essential tools that a programmer might need. into one place so they don't have to switch between a bunch of different programs to get their work done, right? So to simplify it, that's what an IDE is, right? So WinSurf is definitely one of the more popular ones, but probably the most widely used one, even more so than Cursor because of its parent, is GitHub Copilot. So that's Microsoft's, you know, kind of AI-powered copilot coding tool. And this definitely is the broadest IDE support at the lowest premium price point because it's only $10 a month, and they also have free tiers that give you 2,000 completions across all major IDEs. And this kind of functions more as inline code completion versus the full kind of vibe coding experience. And then you do have the option to have the enterprise version. However, we can't even talk about vibe coding. Well, number one, just because GitHub, right? GitHub is kind of like the, I say it's like the online Dropbox, right? How a long time ago, like Dropbox was kind of the, the big category for online storage. So GitHub is kind of like the online storage for, well, a lot of coding, but live coding platforms as well. And then Microsoft's GitHub Copilot, right? Kind of their AI tool of choice there. And then last but not least, the biggest category here might be browser-based app builders. And these are probably your more traditional fully live coding platforms, although the first 2 categories You know, you can vibe code anything, right, from zero all the way to app in those other platforms. But I'd say the browser-based app builders are maybe a little bit more popular. And this is kind of your prompt-to-app platforms. You describe what you want in English and you get a working deployed application. So I'd say probably in this category, Lovable might be one of the more better knowns. And this is essentially prompt-to-deploy full-stack web app for non-developers. They have a new plan mode, which I think has been pretty popular, that previews what the AI will build before writing any code, right? A lot of the other platforms have that. Claude Code has it, Codex has it, et cetera. But that's really helpful, especially if you are using or paying for these platforms via an API, right? If you're plugging in your own, especially these multimodal, or sorry, multimodel vibe coding tools, if you're using your API keys, right? Some of them you just get a monthly plan and different models that are more powerful use more credits, but sometimes you're just plugging in your API keys so they can get expensive. So it is helpful to have something like the plan mode. Lovable also added recently built-in penetration testing, which is super important, and we're gonna get to that later on. And that was kind of a first among vibe coding tools. Next, bold.new. I'd say this is probably one of the fastest kind of paths from prompt to working prototype in your browser. And I also know there's so many other vibe coding tools out there. A lot of them even have become more popular late 2025, early 2026. It was kind of hard once I got to like number 8, You know, I probably had like 6 of them that could have been, you know, number 8, 9, or 10. So a couple of good ones were left off the list, right? But Bolt.new definitely was probably one of the more popular ones in 2024. So this runs entirely in your browser using web containers technology with nothing to install locally. They also have a great free tier plan. And I think this is best for speed demos and quick MVPs, although a lot of users say that overall it's maybe weaker code quality than some of their competitors. Big name in this space, obviously Replit. So that's their, you know, cloud IDE combining an editor, database hosting, and AI agents. So they just launched the agent launch with 10 times more autonomy, building apps across 50+ programming languages. I'm a big fan of the Replit agent. They also have effort-based pricing that scales with actual compute, and real-time multiplayer editing makes it probably one of the stronger platforms for learning and collaboration. Next v0 from Vercel, probably one of the cleanest React and Next.js code from any AI builder. So this generates production-ready components, you know, using Tailwind CSS by default. And this has kind of evolved more into a full-stack JS builder over time. And this is maybe the least lock-in of any platform because you can export standard React code that then you can fully own and use. All right, and then last but definitely not least, One of my favorites that I use probably the most, right, between Codex, um, Claude Code, and then Google's AI Studio, right? I, I, I do use, uh, Google's Antigravity. That's another one that didn't make the list, uh, but I probably use Google's AI Studio a little bit more than Antigravity just because I've been using it for longer and a little more familiar. And, uh, in March, Google did add Antigravity agent support, uh, inside Google AI Studio, Firebase integration, and multiplayer support there as well. And the thing and the simplest way to explain this, well, it's the free, right? They have a great free plan, probably a better free plan than any of the others that I mentioned. It's a free full-stack vibe coding platform powered by everything Gemini. So you can literally in like 5 minutes, you can create a, you know, your own version of something like Nano Banana, right? And then make it, you know, specialized for your niche, right? But obviously if you're in your app, if you're using any of Google's AI, you do have to, you know, provide an API key to power that, Right? It's not like you can just use Nano Banana for free, but you can literally create your own version of any of Google's, you know, AI. And like I said, they do have a generous free tier. And the team over there at Google AI Studio, probably of all of them aside from maybe Claude Code and Codex, kind of, you know, those 2 and then Google AI Studio are just getting so many updates so quickly. All right. So now you know the big tools. You just need to know that this is a growing industry and it is not going anywhere. If you thought vibe coding was gonna come and go and it was just gonna be some trend, no, because vibe coding is turning into vibe working and that's where everyone's going. I mean, even just look at Microsoft, right? Look at some of the things that they've introduced recently, like their Microsoft Claude, or sorry, their Microsoft Copilot Cowork, which is powered by Claude Cowork, right? So it's essentially a vibe coding platform. You know, Microsoft actually has a couple of others, but you know, it's coming to the common knowledge worker, right? And these platforms are growing quickly. So, but there's, there's an issue because right now, 63— a study shows that 63% of vibe coders have never even written a line of code, right, themselves, which is It makes sense, right? Because yes, you do have experienced developers and, you know, people maybe with a little bit of a crossover or background in software development using these, right? And maybe it's allowing them to work in a language that they've never written before. But, you know, it kind of started with, okay, people, you know, using this, maybe they're, you know, more commonly web developers and then they're using it to, you know, launch React apps or something like that. But eventually it's turned into, well, you have people who don't know what code is using these, and these are builders that Aren't just making quick prototypes. They're literally trying to replace enterprise software entirely. And it's actually happened, right? So you have all these stories of like, okay, yeah, you can go vibe code something and use it. That's cute, right? But you're never gonna, you know, replace an enterprise piece of software. Well, companies have, right? I mean, we'll check in with them and see if that's successful. But, you know, one of famous example is, hopefully I get this company right, Autonom. Their head of finance built a full CRM on Lovable reportedly in 3 hours that they used to replace their $40,000 Salesforce contract, right? Zendesk's product team cut prototype timelines from 6 weeks to 3 hours, right? So obviously you have a lot of vibe coding platforms where product teams or software development teams have gone from timelines that were multiple months to, well, less than a day because of vibe coding. So I do think it's a very powerful tool when used by people who absolutely know what they're doing. But just as the market is reaching this everyone's vibe coding, developer trust in AI code is just collapsing. And that's why there's a huge downside to just vibes, right? And going back to that, my little analogy at the beginning of the show, right? If you could just talk your dream home into existence, but you walk in and oh my gosh, the floors are sagging. That's the risk that you run because it's not all good. Yes, if you know what you're doing, vibe coding, obviously is a not just a game changer in terms of what companies can produce, right? Companies that already had software development teams, but companies that didn't, right? Now all of a sudden they can offer new products, new services, new revenue streams to their current clients and customers, right? But it doesn't always work out well because if you don't know what you're doing and you still push something to production, it's obviously extremely problematic. And that's one of the reasons why trust has gone well down. So a Stack Overflow study showed that confidence in AI-generated code actually dropped from 43% to 29% in 2 years. And one of the top frustrations for developers was that AI solutions are almost right, but not quite right. It's almost like, you know, there's more than, you know, one way to write a specific piece of code, right? There's more than one way to design a certain website. And sometimes what we've seen, and maybe this is with some of the companies trying to get more token efficient and not necessarily get things right. Again, that's why, at least for me, sometimes I personally prefer, you know, using, you know, Codex GPT-5.4 Extra High. Yes, it's way slower, but it seemingly gets more things right with fewer issues, right? But that's one of the biggest problems right now is sometimes it might seem like an AI coding app will, you know, The floor. Hey, visually it looks right if we make a cardboard floor or paper-thin floor, but it's not gonna function correctly, right? And I think the industry realized that it was hopelessly hooked on a toolset that it did not actually trust because AI doesn't really care too much, at least by default, about security. That has changed a little bit in 2026, but 2025 was a straight-up security nightmare. nightmare, right? From AppSec Santa 2026 study showed that out of 534 AI code samples, about 25% had confirmed security flaws, right? That's a very high percentage. So if you don't know, as an example, if you don't know how commercial plumbing works in your, you know, Vine-coded house, you're not gonna know that those AI-built pipes were paper, right? A good example of this, which is Multbook, right? So that was an AI-built social network for AI agents. Well, uh, accidentally exposed 1.5 million API tokens from one database misconfiguration. So this is just examples of what can happen if— well, especially as we talk about, uh, agentic coding and, uh, agents coding in loop with sub-agents autonomously, right? It's a little different when you have an experienced human kind of launching the code and testing this out. But when we go straight up agentic, I think that's where we start to run into issues. And when it starts to get, you know, a little bit different, you know, kind of the prospect of demos over memos, I don't think anyone will necessarily complain about. And I do think that's where we're headed. And I think that's why if you're even a non-technical builder, I think in the future it's like no one's gonna want a deck, no one's gonna want an email, They're like, just build me a demo of this now, right? Because you can do this, right? I've actually done this before on calls, right? Someone will be talking about something and be like, here, I just built this. Is this what you're talking about? But if you don't know what you're doing, maybe it's just a demo, right? Maybe it's not something for production because that's where you will run into issues. And another thing is, well, it just generates code. So fast, right? Newer models, once you get over the thinking, the chain of thought, and once it starts spitting out code, it goes so quick. So studies show that fewer and fewer experienced developers are actually reading the code that AI outputs, right? Some of the more famous, you know, kind of developers of the recent, of the last couple, you know, months or quarters have said that they don't even review the code. You know, it was Peter Steinberger, so the OpenCLAW creator who was hired on by OpenAI. So yeah, if you don't know OpenCLAW, it is the most popular piece of open software, open source software, literally ever. And he famously said, or maybe infamously said, I ship code I don't read. And he's not alone, right? Most, you know, you've seen these stories from some of the head devs at Anthropic. People are just saying, yeah, I don't read the code, right? Maybe it's they have a lot of confidence in whatever product that they're using because they're also building it. But it's kind of like if a conveyor belt was cranked to 10x speed and you still just had one quality inspector that's just holding a clipboard, right? There's, it's seemingly as the AI tools get better and smarter, more efficient, well, it seems like, well, we just trust them more. And when engineering teams can't keep up with the amount of code that's spit out, you know, frustrated employees just start building software entirely on their own, right? And I'm talking about that manually, right? More and more people as we start wanting AI and we know what's easy, some engineering teams that are still still, you know, doing AI kind of maybe just code AI-assisted and not totally vibe coding. Well, they're backed up, right? Because now all of a sudden company software stacks have doubled or tripled, right? And what's this led to? Well, it's also IT sprawl, right? It's AI sprawl. So now you have code going into production made by people who maybe shouldn't be deploying code live. But this is also an issue, right? Because engineering teams that are still maybe doing things the quote unquote older school way or just using AI code assist or AI code completion and not straight up vibe coding, right? The demands on them are way more, uh, and you know, non-technical people are just taking this into their own hands. So I always want to talk about this because I think it's important. I do think that vibe coding will, uh, quote unquote destroy traditional software engineering jobs, but I think overall this is going to be a, eventually a a growing field because there's going to be a whole new category of work that did not exist before. And I'm talking about rescue engineering. So here's this kind of, uh, this 90-day, uh, this 3-month, um, kind of realization. So engineers are calling this the 3-month black box effect. This is essentially when an AI-built architecture becomes untouchable, right? This is when the house right, that you went in and built, after 90 days you're like, wait, I forgot everything about this. No one knows which walls are load-bearing. The AI forgets how it built the foundation. Everything stalls, right? So this is what we're seeing from developers. They, number one, everyone's creating exponentially more code. And then we have things like humans are forgetting things. I don't know if you've realized this, pre-AI, I, I think I was smarter, right? I'm not saying that I'm dumber now. I just feel I'm less able to retain information because I'm now with AI, right? With agentic AI, I'm consuming way more information than I was previously, which means I'm forgetting things faster. And it's seemingly, uh, this is a, uh, kind of turning into a global problem where after 90 or so days, right, software teams are just Of forgetting. Not just that, but then also, yes, over the last couple of weeks, month or so, context windows in these programs have gotten better. Yes, but still some of the apps that were built 6 months ago and it took a while to get it approved, but it's been live and now people want updates. Okay, well, we're way past the context window. The human forgot, the AI forgot, infrastructure's changed, right? And maybe the code was shoddy to begin with. So this has led to a completely new category of work, which is rescue engineering. And I think this is one of the hottest new disciplines in tech. So studies have shown that an estimated 8,000 startups now need full or partial rebuilds or refactors of their entire codebase or apps. And those can go anywhere from, you know, $50,000 to $500,000 to a couple million dollars, right? You have a lot of AI startups that essentially vibe coded a very popular platform. They just started stacking duct tape on top of paperclips on top of glue, and then they just realized, oh my gosh, we just realized that our app, it's wildly popular, it's exploding, and it's built on popsicle sticks, right? And they're having to go through and completely redo it. So how do you avoid kind of the fake dream house and build a solid foundation with 5 Here is how you can do it correctly. I think first you have to come to the realization that this is permanent, right? And even if your team may not be vibe coding right now, you will be vibe working, right? Using something like Claude Code, or sorry, Claude Cowork, using something like Microsoft Copilot Cowork, something like the, you know, whatever the Codex ChatGPT super app becomes. This is going to become very common where we are going to be using natural language to build little apps, right? Maybe it's to build apps to finish our work faster. Maybe it's to build apps for consumers. Maybe it's replacing little pieces of software, updating pieces of software. Non-technical people are going to be doing it. So you need to follow these rules, but also you need to understand the companies riding the waves without governance are going to pay for that rescue engineering in the breach cost. But the companies treating AI coding as a rigorous engineering kind of problem with human oversight are going to capture the real value. Because like I said, this technology is not optional, but how your organization governs it is entirely your choice. All right, I hope this one was helpful, taking a quick-ish look at the vibe coding boom and why vibe coding isn't going away and how it's both good and bad. All right. Should we do more vibe coding? Right? Let me know. I'm always on the fence about this, right? Especially from a podcast perspective. I'd like to have something for you all that you can just kind of listen to in your car, you know, listen to when you're on the treadmill, walking your dog, whatever it is, and not necessarily have to be watching something on the screen at all times. So if we should be covering more on vibe coding, let me know. But if this was helpful, you're definitely gonna love the rest of our Start Here series. Remember, this is kind of made to listen to in order. They're shorter episodes. All right. So make sure you go to starthearseries.com. That's gonna get you free access to our inner circle community, and you can go listen to all of the episodes in order. So thank you for tuning in. Hope to see you back tomorrow and every day for more Everyday AI. Thanks, y'all.

And that's a wrap for today's edition of Everyday AI. Thanks for joining us. If you enjoyed this episode, please subscribe and leave us a rating. It helps keep us going. For a little more AI magic, visit youreverydayai.com and sign up to our daily newsletter so you don't get left behind. Go break some barriers, and we'll see you next time.