WEBVTT 00:00:00.000 --> 00:00:03.399 Sam Altman, the OpenAI CEO, he talked about this 00:00:03.399 --> 00:00:05.740 profound shift. He called it the era of the idea 00:00:05.740 --> 00:00:07.799 guy. Yeah. And for the longest time, the real 00:00:07.799 --> 00:00:10.560 wall, the barrier to building an app was just, 00:00:10.560 --> 00:00:13.160 could you write the code? That's kind of gone 00:00:13.160 --> 00:00:16.440 now, that technical gate. I agree. It feels like 00:00:16.440 --> 00:00:20.120 AI can do so much of the heavy lifting. But the 00:00:20.120 --> 00:00:22.809 challenge hasn't. disappeared has it it's just 00:00:22.809 --> 00:00:25.190 changed now it feels like information overload 00:00:25.190 --> 00:00:28.429 so many options exactly finding the right tool 00:00:28.429 --> 00:00:30.210 the one that actually fits what you want to build 00:00:30.210 --> 00:00:32.670 and you know how technical you are that's the 00:00:32.670 --> 00:00:35.170 new struggle so this deep dive we're going to 00:00:35.170 --> 00:00:37.409 cut through that noise right so our mission today 00:00:37.409 --> 00:00:40.390 is to really look at the sources and figure out 00:00:40.390 --> 00:00:43.109 which of these vibe coding tools are actually 00:00:43.109 --> 00:00:45.630 standing out we need to separate the signal from 00:00:45.630 --> 00:00:49.270 the noise for, well, technical users, non -technical 00:00:49.270 --> 00:00:52.310 builders, and that growing group of mobile developers, 00:00:52.549 --> 00:00:54.090 too. And we should probably define that term 00:00:54.090 --> 00:00:56.850 first, right? Vibe coding. It's not just about 00:00:56.850 --> 00:00:58.729 coding faster. No. What's really interesting 00:00:58.729 --> 00:01:01.429 here is how it describes this new dynamic, this 00:01:01.429 --> 00:01:04.049 collaboration. Totally. You bring the vision, 00:01:04.569 --> 00:01:08.730 the vibe, and the AI does the translation. It 00:01:08.730 --> 00:01:11.010 handles all that technical stuff you maybe don't 00:01:11.010 --> 00:01:13.989 want to touch. It's a partnership, really. And 00:01:13.989 --> 00:01:16.099 these tools... They exist on a spectrum, don't 00:01:16.099 --> 00:01:18.299 they? Oh, absolutely. On one end, you've got 00:01:18.299 --> 00:01:20.480 the super newbie friendly ones. You can literally 00:01:20.480 --> 00:01:23.260 just describe what you want in plain English, 00:01:23.319 --> 00:01:26.079 like, I need a contact form, make the button 00:01:26.079 --> 00:01:28.540 blue, and poof, it appears. Zero code needed. 00:01:28.659 --> 00:01:31.420 And then the other end, tools for actual developers. 00:01:31.659 --> 00:01:35.159 Exactly. For them, the AI is more like a... a 00:01:35.159 --> 00:01:37.379 super intelligent assistant. You still gotta 00:01:37.379 --> 00:01:39.480 understand the basics, like front end versus 00:01:39.480 --> 00:01:42.340 back end. Knowing where a tool sits on that spectrum 00:01:42.340 --> 00:01:44.920 is, well, essential. Okay, let's dig into that. 00:01:44.939 --> 00:01:47.959 Let's start with the big guns. The tools for 00:01:47.959 --> 00:01:49.760 people who are already comfortable, you know, 00:01:49.959 --> 00:01:52.260 opening a terminal, running an NPM install. Yeah, 00:01:52.420 --> 00:01:54.400 the sources are super clear on this. For that 00:01:54.400 --> 00:01:57.780 technical crowd, one name keeps coming up, cursor. 00:01:58.079 --> 00:02:00.519 Cursor. Why does it keep getting ranked so highly, 00:02:00.739 --> 00:02:03.239 like S plus tier, for serious devs? It sounds 00:02:03.239 --> 00:02:04.879 like it all comes down to this thing they call 00:02:04.879 --> 00:02:07.120 agent architecture. That's the whole ball game 00:02:07.120 --> 00:02:10.819 right there. See, an AI agent. It's doing way 00:02:10.819 --> 00:02:12.639 more than just spitting out a code block for 00:02:12.639 --> 00:02:14.860 you to copy and paste. OK, so for someone listening 00:02:14.860 --> 00:02:17.919 who maybe doesn't live in the command line, what's 00:02:17.919 --> 00:02:20.860 this agent architecture actually doing? Think 00:02:20.860 --> 00:02:23.639 of it like a smart layer around the main AI model. 00:02:24.000 --> 00:02:26.500 This agent, it reads all your project files, 00:02:26.740 --> 00:02:28.879 it understands the context of your code, makes 00:02:28.879 --> 00:02:31.939 really precise changes. And this is key. It writes 00:02:31.939 --> 00:02:34.379 those changes back into the right place in your 00:02:34.379 --> 00:02:37.219 files. It doesn't just suggest, it acts within 00:02:37.219 --> 00:02:41.039 your code base. Ah, OK. That interaction, that's 00:02:41.039 --> 00:02:43.300 the real difference maker. And I noticed the 00:02:43.300 --> 00:02:45.560 sources also mentioned the community around cursor. 00:02:45.960 --> 00:02:48.180 That's always a big plus for developers. Yeah. 00:02:48.360 --> 00:02:50.379 They compared its growth to React back in the 00:02:50.379 --> 00:02:52.509 day. Which means if you run into a problem, you're 00:02:52.509 --> 00:02:55.469 not stuck alone. There are tons of guides, discussions, 00:02:55.789 --> 00:02:58.229 forums. Help is out there. That's invaluable, 00:02:58.370 --> 00:03:00.610 that resource depth. And there was that specific 00:03:00.610 --> 00:03:03.569 example, right? Using cursor to fix a 500 internal 00:03:03.569 --> 00:03:06.009 server error. Right. Instead of you digging through 00:03:06.009 --> 00:03:08.250 log files for hours, you just prompt cursor. 00:03:08.750 --> 00:03:11.389 Like, hey, check the login stuff and the database 00:03:11.389 --> 00:03:15.189 connection in auth .js and database .js. And 00:03:15.189 --> 00:03:17.969 it can diagnose and fix it all from one request. 00:03:18.389 --> 00:03:21.169 That's serious power. Okay, but what about the 00:03:21.169 --> 00:03:24.349 competition? Anthropics clawed code. It used 00:03:24.349 --> 00:03:27.050 to be right up there, but the feeling seems to 00:03:27.050 --> 00:03:29.830 be changing. Yeah, the word on the street or 00:03:29.830 --> 00:03:32.550 the community consensus is that it's been nerfed. 00:03:32.969 --> 00:03:35.009 That's a gaming term, right? It means something 00:03:35.009 --> 00:03:37.569 got weaker. Developers feel its code -writing 00:03:37.569 --> 00:03:40.629 chops aren't quite what they used to be. So here's 00:03:40.629 --> 00:03:42.370 the thing that really struck me, connecting back 00:03:42.370 --> 00:03:45.509 to that agent idea. How can cursor perform better 00:03:45.509 --> 00:03:49.710 if, sometimes, They're using the exact same underlying 00:03:49.710 --> 00:03:53.349 AI model, like cloud sonnet 3 .5. The sources 00:03:53.349 --> 00:03:55.289 seemed quite clear on this difference. And that's 00:03:55.289 --> 00:03:57.469 where the whole agent lesson really lands. Explain 00:03:57.469 --> 00:03:59.750 that a bit more. OK, so think of the AI model, 00:04:00.150 --> 00:04:02.729 like sonnet 3 .5, as the brain. It's got the 00:04:02.729 --> 00:04:05.590 raw intelligence. But the agent, that's the hands 00:04:05.590 --> 00:04:09.060 and the eyes. Cursor, right now, seems to have 00:04:09.060 --> 00:04:11.300 better hands for writing the code precisely and 00:04:11.300 --> 00:04:13.060 better eyes for reading your files and understanding 00:04:13.060 --> 00:04:16.600 the context. So same brain, maybe, but Cursor's 00:04:16.600 --> 00:04:18.139 got a better way of interacting with the world, 00:04:18.199 --> 00:04:20.519 with your code. So is it fair to say the core 00:04:20.519 --> 00:04:23.819 AI model is maybe becoming a commodity? And the 00:04:23.819 --> 00:04:26.639 agent architecture, that's the real differentiator 00:04:26.639 --> 00:04:29.399 now? By building anything serious, yeah. That 00:04:29.399 --> 00:04:31.339 architecture, how it actually executes the code 00:04:31.339 --> 00:04:33.620 and interacts with files, that determines success. 00:04:33.819 --> 00:04:36.540 Let's pivot then. Let's talk about the pure idea 00:04:36.540 --> 00:04:40.019 guy or gal, the person with the vision, but maybe 00:04:40.019 --> 00:04:43.620 not the CS degree. If cursor is too much, where 00:04:43.620 --> 00:04:45.759 should they start? For that non -technical builder, 00:04:45.939 --> 00:04:48.060 the sources point pretty clearly to v0. It's 00:04:48.060 --> 00:04:50.399 made by Vercell. That's the top pick. If v0 seems 00:04:50.399 --> 00:04:52.639 to hit that sweet spot, right? Powerful enough 00:04:52.639 --> 00:04:54.560 for real results, but still easy to get started 00:04:54.560 --> 00:04:57.079 with. Exactly. v0 gives you stuff you can actually 00:04:57.079 --> 00:04:59.779 launch quickly. And the source has highlighted 00:04:59.779 --> 00:05:02.660 two big things. It's integration marketplace. 00:05:03.079 --> 00:05:05.339 And the template library. The marketplace. Yeah. 00:05:05.500 --> 00:05:08.040 So you get choices for databases, logins, that 00:05:08.040 --> 00:05:11.000 kind of thing. That sounds crucial for avoiding 00:05:11.000 --> 00:05:13.339 getting locked into one vendor later. Totally. 00:05:13.699 --> 00:05:15.560 And the template library. It means you're not 00:05:15.560 --> 00:05:17.439 starting from scratch. You get pre -built components 00:05:17.439 --> 00:05:20.120 that look good, saves a ton of time up front. 00:05:20.399 --> 00:05:22.939 I love that test mentioned in the sources where 00:05:22.939 --> 00:05:26.300 v0 was the only tool that didn't, like, freeze 00:05:26.300 --> 00:05:29.439 up when building a complex wedding RSVP site 00:05:29.439 --> 00:05:32.040 with lots of steps. That says a lot about its 00:05:32.040 --> 00:05:34.000 stability. Yeah, if you're serious about building 00:05:34.000 --> 00:05:36.100 something that needs to grow and handle real 00:05:36.100 --> 00:05:38.800 use, vZero seems to have that solid foundation. 00:05:38.980 --> 00:05:40.720 So you could literally just prompt it with something 00:05:40.720 --> 00:05:43.300 like, make a home page for a coffee shop, it 00:05:43.300 --> 00:05:45.379 needs an app bar, an about section, a menu, and 00:05:45.379 --> 00:05:47.439 three columns, and stick a Google map in there, 00:05:47.439 --> 00:05:50.339 and it would just do it. Pretty much. That's 00:05:50.339 --> 00:05:52.339 the goal. Now, there are simpler options, too, 00:05:52.339 --> 00:05:54.879 like lovable and bold. They're kind of B tier. 00:05:55.240 --> 00:05:57.420 Right. They got popular because they hide all 00:05:57.420 --> 00:05:59.160 that tricky backend stuff, didn't they, like 00:05:59.160 --> 00:06:02.120 setting up servers and API keys? Yeah. They make 00:06:02.120 --> 00:06:05.379 it super simple to start. But that simplicity 00:06:05.379 --> 00:06:08.160 costs you flexibility. Lovable, for instance, 00:06:08.480 --> 00:06:10.959 often kind of pushes you towards using SuperBase 00:06:10.959 --> 00:06:14.240 for your database. SuperBase is fine, great for 00:06:14.240 --> 00:06:16.579 starting fast. But what if you want to change 00:06:16.579 --> 00:06:19.740 later? You might be stuck. So great for a quick 00:06:19.740 --> 00:06:22.319 prototype, maybe testing an idea? Perfect for 00:06:22.319 --> 00:06:24.319 that. But if you think your app might get bigger, 00:06:24.579 --> 00:06:26.819 you could hit a wall pretty fast. That hidden 00:06:26.819 --> 00:06:30.519 complexity can bite you, honestly. I still wrestle 00:06:30.519 --> 00:06:32.420 with prompt drift myself sometimes when I'm trying 00:06:32.420 --> 00:06:34.860 to push a tool hard on a complex build. Wait, 00:06:34.879 --> 00:06:36.759 even you hit prompt drift, what does that feel 00:06:36.759 --> 00:06:39.079 like? Is the tool just breaking or forgetting 00:06:39.079 --> 00:06:42.339 what you asked it? It feels like the AI loses 00:06:42.339 --> 00:06:45.730 the thread. you know after maybe 20 prompts it 00:06:45.730 --> 00:06:47.730 forgets the style guide you set up way back on 00:06:47.730 --> 00:06:49.769 prompt three or a constraint you mentioned the 00:06:49.769 --> 00:06:51.750 output just starts getting worse it takes patience 00:06:51.750 --> 00:06:53.769 you got to keep reminding it reframe your prompts 00:06:53.769 --> 00:06:57.149 okay that's insightful so back to v0 versus the 00:06:57.149 --> 00:07:01.110 simpler tools if v0 offers more flexibility but 00:07:01.110 --> 00:07:03.910 relies on a big company like vercel isn't that 00:07:03.910 --> 00:07:06.629 kind of against the whole solo builder idea that 00:07:06.629 --> 00:07:09.009 maybe lovable taps into it's definitely a trade 00:07:09.009 --> 00:07:11.829 -off v0 gives you that stability that huge feature 00:07:11.829 --> 00:07:14.889 set backed by vercel lovable or bold. They give 00:07:14.889 --> 00:07:17.089 you that instant gratification, that super fast 00:07:17.089 --> 00:07:20.050 start, a much gentler learning curve for someone 00:07:20.050 --> 00:07:22.129 just dipping their toes in. It depends on what 00:07:22.129 --> 00:07:24.689 you prioritize right now. Mid -roll sponsor break. 00:07:25.129 --> 00:07:27.829 Welcome back to the deep dive. All right, let's 00:07:27.829 --> 00:07:30.149 shift gears into what's emerging. There's a lot 00:07:30.149 --> 00:07:33.110 of buzz around using vibe coding for specifically 00:07:33.360 --> 00:07:35.639 mobile apps. Yeah, mobile is definitely having 00:07:35.639 --> 00:07:37.420 a moment. You see it all over TikTok, right? 00:07:37.560 --> 00:07:40.000 Some simple, useful app just blows up, gets tons 00:07:40.000 --> 00:07:41.779 of downloads. But the old way was tough. You 00:07:41.779 --> 00:07:43.879 basically had to learn two completely different, 00:07:44.100 --> 00:07:46.600 pretty complex languages. Swift for iPhones, 00:07:47.019 --> 00:07:50.610 Kotlin for Android. Exactly. But these new tools 00:07:50.610 --> 00:07:53.550 names like Rorik, Build .ai, anything, they're 00:07:53.550 --> 00:07:55.970 changing that. The sources suggest they're probably 00:07:55.970 --> 00:07:58.509 using something called Expo under the hood. Expo 00:07:58.509 --> 00:08:00.529 lets you build your app once and then deploy 00:08:00.529 --> 00:08:03.629 it to both iOS and Android. That's huge. A massive 00:08:03.629 --> 00:08:05.850 time saver. They're still kind of B tier, maybe 00:08:05.850 --> 00:08:08.410 early days. But wow, that really opens things 00:08:08.410 --> 00:08:11.189 up for smaller niche mobile apps. Definitely. 00:08:11.389 --> 00:08:13.910 And speaking of big players, we can't ignore 00:08:13.910 --> 00:08:18.769 the 800 pound gorilla. OpenAI, ChatGPT, and its 00:08:18.769 --> 00:08:21.110 API, it's really becoming a contender in the 00:08:21.110 --> 00:08:23.529 coding space. Yeah, just a few months back, ChatGPT 00:08:23.529 --> 00:08:27.709 for code was decent. But now, the sources are 00:08:27.709 --> 00:08:29.389 saying it's seriously competitive with things 00:08:29.389 --> 00:08:31.870 like Cloud Sonnet 3 .5. Well, they have massive 00:08:31.870 --> 00:08:34.409 resources, right? And Microsoft backing. It's 00:08:34.409 --> 00:08:36.289 probably not smart to bet against Sam Altman 00:08:36.289 --> 00:08:38.070 here. It's become a really strong, versatile 00:08:38.070 --> 00:08:40.009 option for both developers and non -technical 00:08:40.009 --> 00:08:43.350 folks. So it sits kind of just below that specialized 00:08:43.350 --> 00:08:45.610 agent stuff like Cursor, but definitely a step 00:08:45.610 --> 00:08:47.549 up. from those simpler B -tier tools. Right. 00:08:47.730 --> 00:08:49.909 Now, we also need to talk about a warning. Windsurf. 00:08:50.250 --> 00:08:52.830 The sources put it way down in D -tier, even 00:08:52.830 --> 00:08:55.009 though the tech might have been okay. A warning? 00:08:55.149 --> 00:08:57.809 Why? It comes down to trust. Really, the founder 00:08:57.809 --> 00:09:01.429 just... left. Suddenly. And then the team got 00:09:01.429 --> 00:09:04.169 bought by Devon. If you'd invested time, maybe 00:09:04.169 --> 00:09:07.049 money, learning Windsurf, that kind of business 00:09:07.049 --> 00:09:09.970 chaos is a huge red flag. So even if the technology 00:09:09.970 --> 00:09:12.070 worked, the instability around the business makes 00:09:12.070 --> 00:09:14.389 it just too risky to build anything serious on. 00:09:14.600 --> 00:09:17.779 Absolutely. There are just too many good, stable 00:09:17.779 --> 00:09:20.200 options out there to gamble on a platform that 00:09:20.200 --> 00:09:22.519 might just disappear or radically change next 00:09:22.519 --> 00:09:24.919 month. Okay. And there was one more interesting 00:09:24.919 --> 00:09:28.389 one, kind of a dark horse. Chef. from Convex, 00:09:28.710 --> 00:09:30.529 but it wasn't built to compete directly, was 00:09:30.529 --> 00:09:32.730 it? No, Chef has a really unique angle. It's 00:09:32.730 --> 00:09:34.870 basically a showcase for Convex, which is their 00:09:34.870 --> 00:09:37.389 backend platform. They want other vibe coding 00:09:37.389 --> 00:09:41.269 tools to use Convex, so Chef is free, open source. 00:09:41.289 --> 00:09:43.570 You can even copy it, fork it, and build your 00:09:43.570 --> 00:09:45.789 own custom thing. It's like a demo, but a really 00:09:45.789 --> 00:09:48.409 functional one. So thinking about that Windsurf 00:09:48.409 --> 00:09:51.210 situation, how much should people weigh that 00:09:51.210 --> 00:09:53.769 business stability against just the raw technical 00:09:53.769 --> 00:09:55.830 power of a tool, especially when things are changing 00:09:55.830 --> 00:09:58.720 so fast? Honestly, for anything you plan to rely 00:09:58.720 --> 00:10:01.960 on long term, stability wins. Good tech on a 00:10:01.960 --> 00:10:04.360 shaky foundation isn't worth the risk. OK, so 00:10:04.360 --> 00:10:06.240 we've mapped out the landscape. Let's try and 00:10:06.240 --> 00:10:09.639 boil this down. Simple, actionable advice for 00:10:09.639 --> 00:10:12.440 someone listening who wants to get started in 00:10:12.440 --> 00:10:15.919 this era of the idea guy. We can make it pretty 00:10:15.919 --> 00:10:17.840 straightforward. If you're technical, you need 00:10:17.840 --> 00:10:20.039 that fine -grained control, that file interaction. 00:10:20.519 --> 00:10:22.820 Go with cursor. And if you're more on the non 00:10:22.820 --> 00:10:25.000 -technical side, you have the vision, but not 00:10:25.000 --> 00:10:28.600 the code background. Start with V0. That mix 00:10:28.600 --> 00:10:31.259 of quality output and ease of use seems hard 00:10:31.259 --> 00:10:33.460 to beat right now. Yep. And if mobile apps are 00:10:33.460 --> 00:10:35.179 your specific goal, then yeah, start playing 00:10:35.179 --> 00:10:38.340 around with work. Build .ai or anything. But 00:10:38.340 --> 00:10:40.259 keep an eye on them. It's a new space. Things 00:10:40.259 --> 00:10:42.779 will move fast. And here's a tip that often gets 00:10:42.779 --> 00:10:44.720 overlooked, but can really matter for sticking 00:10:44.720 --> 00:10:47.549 with it. Follow the founders. Yeah. Connect with 00:10:47.549 --> 00:10:49.870 the people behind the tools, like Yermo Rauch 00:10:49.870 --> 00:10:53.950 at vZero, Sam Altman at OpenAI, Anton Osika at 00:10:53.950 --> 00:10:56.490 Lovable. When you kind of buy into their vision, 00:10:56.629 --> 00:10:58.789 their long -term plan for the platform, you're 00:10:58.789 --> 00:11:00.669 just more likely to stay committed and push through 00:11:00.669 --> 00:11:02.690 the tough spots. But maybe the biggest thing 00:11:02.690 --> 00:11:05.470 required, the absolute essential, the mindset 00:11:05.470 --> 00:11:07.950 shift, especially for newcomers. This is the 00:11:07.950 --> 00:11:11.090 hard truth part. Building software. It still 00:11:11.090 --> 00:11:14.389 takes time, even with amazing AI help. You got 00:11:14.389 --> 00:11:17.090 to set realistic expectations. Right. Don't get 00:11:17.090 --> 00:11:18.990 bummed out if your first try kind of falls apart 00:11:18.990 --> 00:11:21.509 after five prompts. That's totally normal. It's 00:11:21.509 --> 00:11:23.429 part of the process. Building stuff is messy. 00:11:23.690 --> 00:11:26.320 Your first version probably going to break. It 00:11:26.320 --> 00:11:29.059 needs planning, testing, just sticking with it. 00:11:29.120 --> 00:11:30.980 It's like, ah, going to the gym, right? You get 00:11:30.980 --> 00:11:33.679 results from consistency, not just from trying 00:11:33.679 --> 00:11:35.779 the first magic shortcut you find. So the best 00:11:35.779 --> 00:11:38.740 advice might be plan before you prompt. Maybe 00:11:38.740 --> 00:11:41.120 use something like ChatGPT just to sketch out 00:11:41.120 --> 00:11:43.779 the logic, the flow of your app before you even 00:11:43.779 --> 00:11:45.919 jump into the coding tool. Don't just start typing 00:11:45.919 --> 00:11:48.519 into a blank slate. Totally. And just to circle 00:11:48.519 --> 00:11:50.799 back and wrap up, let's hit that core technical 00:11:50.799 --> 00:11:54.049 idea again. The agent. We saw how the quality 00:11:54.049 --> 00:11:57.009 of that agent layer, the hands and eyes, is why 00:11:57.009 --> 00:11:59.330 cursor might outperform Claude, even with the 00:11:59.330 --> 00:12:01.990 same brain. Yeah, it's the quality of that architecture 00:12:01.990 --> 00:12:05.590 that really dictates how well the tool can read 00:12:05.590 --> 00:12:08.450 your code, make changes, and actually interact 00:12:08.450 --> 00:12:10.789 with your project files. It really makes you 00:12:10.789 --> 00:12:13.370 stop and think, whoa, imagine scaling that kind 00:12:13.370 --> 00:12:17.269 of precise agent architecture up, handling Like 00:12:17.269 --> 00:12:20.230 a billion complex coding requests every single 00:12:20.230 --> 00:12:22.870 day. The engineering challenge there is just 00:12:22.870 --> 00:12:25.230 mind boggling. It really points back to the main 00:12:25.230 --> 00:12:27.909 takeaway from all this, doesn't it? Success now, 00:12:28.090 --> 00:12:31.389 in this era of the idea guy, it depends less 00:12:31.389 --> 00:12:33.330 on whether you already know how to code. And 00:12:33.330 --> 00:12:35.870 way more on picking the right tool architecture, 00:12:36.110 --> 00:12:38.129 understanding that agent versus model difference, 00:12:38.129 --> 00:12:40.789 and honestly, just having the patience to see 00:12:40.789 --> 00:12:43.230 it through, to build something real. So the core 00:12:43.230 --> 00:12:45.809 advice is simple. Stop endlessly debating the 00:12:45.809 --> 00:12:48.120 tools. Pick one of these solid options we talked 00:12:48.120 --> 00:12:50.419 about and just start building something. Give 00:12:50.419 --> 00:12:52.340 yourself permission to mess up and learn as you 00:12:52.340 --> 00:12:55.100 go. Your first try might feel clunky, sure. Yeah. 00:12:55.200 --> 00:12:57.039 But by the time you get to your third or fourth 00:12:57.039 --> 00:13:00.120 version, you'll probably genuinely amaze yourself 00:13:00.120 --> 00:13:02.559 with what you can create now. The tools are here. 00:13:03.179 --> 00:13:04.919 The community is growing like crazy. Really, 00:13:05.039 --> 00:13:06.659 the only question left for you, the listener, 00:13:06.860 --> 00:13:09.000 is, yeah, what are you going to build? Oh, TRU 00:13:09.000 --> 00:13:09.299 music.