Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
(00:00):
Hi everyone.
(00:00):
I'm Andy, and this is the AI breakdown.
Today we're exploring vibe coding, a groundbreaking shift that's turning the tech world on its head at its heart vibe Coding means building software through conversation rather than traditional programming.
You simply describe what you want in natural language, and the AI generates the actual code, and you guide the process through conversation based on feel and intuition.
(00:26):
This technology has evolved at lightning speed.
It's only seven months since Andre Carpathy coined the term and it's already gaining serious traction around a quarter of why Combinator's latest startups are reportedly building with 95% AI generated code a surge that's being closely tied to this movement and lovable the poster child of vibe coding.
(00:49):
Shot up to $100 million a RR and a $1.8
billion valuation in just eight months.
Today's episode will unpack what vibe coding really is, why it's gaining momentum, whether it's ready for real software development, and where this movement could take us.
.93712716Next, let's break down what vibe coding really is and what it isn't.
11
00:01:15,572.93712716 --> 00:01:20,282.93712716
At its core, it's about handing over the wheel and letting AI generate the code.
12
00:01:20,762.93712716 --> 00:01:23,97.93712716
You're not slogging through syntax line by line.
13
00:01:23,747.93712716 --> 00:01:24,977.93712716
You're more like a conductor.
14
00:01:25,397.93712716 --> 00:01:30,557.93712716
You set the vision, describe what you want, request tweaks, and shape the feel of the product.
15
00:01:31,97.93712716 --> 00:01:36,227.93712716
As carpathy put it fully, give into the vibes and forget that code even exists.
16
00:01:36,947.93712716 --> 00:01:38,207.93712716
That's a key distinction.
17
00:01:38,507.93712716 --> 00:01:43,817.93712716
If you're painstakingly reviewing, testing and understanding every line, the AI spits out.
18
00:01:44,237.93712716 --> 00:01:47,777.93712716
You're not vibe coding, you're just doing AI assisted development.
19
00:01:48,197.93712716 --> 00:01:48,827.93712716
True vibe.
20
00:01:48,827.93712716 --> 00:01:51,107.93712716
Coding is hands off and outcome driven.
21
00:01:51,497.93712716 --> 00:01:54,797.93712716
Of course, sometimes what arrives looks nothing like what you ordered.
22
00:01:55,187.93712716 --> 00:01:57,557.93712716
That unpredictability is part of the deal.
23
00:01:57,917.93712716 --> 00:01:58,967.93712716
And here's the tension.
24
00:01:58,997.93712716 --> 00:02:02,87.93712716
The upside is massive, but the risks are just as big.
25
00:02:02,807.93712716 --> 00:02:09,707.93712716
Veracode recently published research that found nearly half of AI generated code carried serious security flaws.
26
00:02:10,127.93712716 --> 00:02:16,427.93712716
And while I get they have an agenda here, the point is the code can be flawed and this stuff needs human oversight.
27
00:02:17,177.93712716 --> 00:02:25,697.93712716
In a recent incident, one of rep's, AI agents went rogue and wiped a live production database after being told multiple times not to touch it.
28
00:02:26,117.93712716 --> 00:02:29,717.93712716
The promise here is groundbreaking, but the safety rails are flimsy.
29
00:02:30,347.93712716 --> 00:02:32,267.93712716
Personally, I'm provi coding.
30
00:02:32,567.93712716 --> 00:02:42,977.93712716
I believe natural language will become the default gateway for building software, but I've also lost evenings stuck in vibe loops, watching the AI wander off track while burning through credits.
31
00:02:43,637.93712716 --> 00:02:50,507.93712716
Right now, these tools are brilliant for prototyping, discovery, and rapid experimentation for mission critical builds.
32
00:02:50,507.93712716 --> 00:02:57,257.93712716
Though we're not there yet, we've also got to be careful not to conflate AI assisted developments with vibe coding.
33
00:02:57,737.93712716 --> 00:02:58,427.93712716
This matters.
34
00:02:58,427.93712716 --> 00:03:01,787.93712716
When we look at why Combinators latest cohort I mentioned earlier.
35
00:03:02,297.93712716 --> 00:03:10,817.93712716
Some people point to that stat, a quarter of startups building with 95% AI generated code as evidence of vibe codings rise.
36
00:03:11,147.93712716 --> 00:03:14,177.93712716
But the reality is most of those founders are highly technical.
37
00:03:14,717.93712716 --> 00:03:21,167.93712716
What we're really seeing is rapid adoption of AI coding workflows, not pure vibe coding in the strictest sense.
38
00:03:21,437.93712716 --> 00:03:22,157.93712716
My guess.
39
00:03:22,562.93712716 --> 00:03:29,312.93712716
They're still applying plenty of rigorous oversight, not fully forgetting code exists the way Carpathy suggested.
40
00:03:29,882.93712716 --> 00:03:37,52.93712716
So why did Vibe Coding explode this year? It's the collision of a tech leap and a cultural shift on the tech side.
41
00:03:37,322.93712716 --> 00:03:42,302.93712716
AI models like Claude and GPT have massively leveled up their coding skills.
42
00:03:42,812.93712716 --> 00:03:50,402.93712716
Then came the expanding context windows, which meant your AI could suddenly take in your whole code base, not just a single file.
43
00:03:51,242.93712716 --> 00:03:51,902.93712716
That shift.
44
00:03:51,932.93712716 --> 00:04:00,752.93712716
Let AI understand entire projects, spot connections, and produce multi-step context aware solutions, but tech alone doesn't create a movement.
45
00:04:01,142.93712716 --> 00:04:09,662.93712716
What really lit the fuse were platforms like lovable PLT and Bolt new, making this magic accessible to everyone, not just developers.
46
00:04:10,292.93712716 --> 00:04:18,272.93712716
Suddenly non-technical professionals and entrepreneurs could turn their ideas into software just by having a conversation with ai.
47
00:04:19,112.93712716 --> 00:04:24,422.93712716
This cultural shift unleashed a wave of innovation where the barrier to entry plummeted overnight.
48
00:04:24,992.93712716 --> 00:04:33,542.93712716
For example, vibe coding is being used as a startup enablement tool, letting founders move from idea to prototype in days instead of months.
49
00:04:34,232.93712716 --> 00:04:46,532.93712716
Instead of needing a full engineering team up front, a small founding crew or even a solo founder can spin up working dashboards, simple apps, or customer demos through conversation with an ai.
50
00:04:47,72.93712716 --> 00:04:55,832.93712716
That means less capital burned on early stage development, faster validation of product market fit, and more agility to pivot when things don't land.
51
00:04:57,280.23469359 --> 00:04:58,90.23469359
But here's the thing.
52
00:04:58,660.23469359 --> 00:05:03,910.23469359
Real successful examples of software born from true vibe coding are still pretty rare.
53
00:05:04,330.23469359 --> 00:05:14,200.23469359
These tools are new and while they're brilliant for prototypes and early traction, most companies that scale up eventually re-platform or bring in engineers to harden the product.
54
00:05:14,725.23469359 --> 00:05:17,725.23469359
That said, there are some standout stories worth calling out.
55
00:05:18,145.23469359 --> 00:05:19,255.23469359
Take Table one.
56
00:05:19,555.23469359 --> 00:05:21,505.23469359
A New York Restaurant Reservations app.
57
00:05:22,45.23469359 --> 00:05:28,75.23469359
Its co-founder Tarek Arafat vibe coded the first landing page on Lovable in just a few days.
58
00:05:28,495.23469359 --> 00:05:34,135.23469359
That single page helped him raise $400,000 in four days and get the product off the ground.
59
00:05:34,525.23469359 --> 00:05:41,275.23469359
The app now has tens of thousands of downloads, thousands of paying users, and has already seeded over a hundred thousand diners.
60
00:05:42,145.23469359 --> 00:05:49,555.23469359
It's been featured in Forbes and The New Yorker Proof that a vibe coated foundation can evolve into a credible high growth startup.
61
00:05:50,305.23469359 --> 00:05:53,545.23469359
Another example comes from the WordPress community publisher.
62
00:05:53,545.23469359 --> 00:05:58,165.23469359
Matt Madero used Bolt New to spin up a suite of niche web apps for his audience.
63
00:05:58,555.23469359 --> 00:05:59,155.23469359
Things like podcast power.
64
00:06:00,325.23469359 --> 00:06:03,745.23469359
A WordPress News Tracker, even a little game for his community.
65
00:06:04,105.23469359 --> 00:06:13,405.23469359
He's not a full-time engineer, but with Bolt, he was able to create polished branded apps quickly enough to add real value for his audience and boost his reputation.
66
00:06:14,155.23469359 --> 00:06:19,765.23469359
These stories show the potential vibe coding can take someone from idea to product shockingly fast.
67
00:06:20,140.23469359 --> 00:06:25,720.23469359
But they also underline the reality success stories, like these are still the exception, not the rule.
68
00:06:26,410.23469359 --> 00:06:31,210.23469359
Most five coded projects today are demos, experiments, or MVPs.
69
00:06:31,660.23469359 --> 00:06:40,420.23469359
We're in that early no-code phase where the hype is high, the creativity is exploding, but the big scaled businesses are still thin on the ground.
70
00:06:41,20.23469359 --> 00:06:44,110.23469359
And for me personally, I love the discovery angle vibe.
71
00:06:44,110.23469359 --> 00:06:47,440.23469359
Coding feels like a creative partner when I'm exploring ideas.
72
00:06:47,830.23469359 --> 00:06:50,560.23469359
Pulling my thoughts together and testing possibilities.
73
00:06:50,980.23469359 --> 00:06:59,140.23469359
It lets me rapidly explore directions I wouldn't have considered on my own, often sparking new concepts that build on and expand my original ideas.
74
00:06:59,800.23469359 --> 00:07:02,920.23469359
Let's talk about the money, the tools, and the reality check.
75
00:07:03,340.23469359 --> 00:07:04,720.23469359
The market numbers are staggering.
76
00:07:05,110.23469359 --> 00:07:10,210.23469359
Analysts expect vibe coding to be a $26 billion industry by 2030.
77
00:07:10,570.23469359 --> 00:07:15,730.23469359
And like I said, lovable went from zero to a hundred million a RR in just eight months.
78
00:07:16,360.23469359 --> 00:07:18,550.23469359
Faster than any software company in history.
79
00:07:19,947.21663344 --> 00:07:30,777.21663344
But here's the real question, which tools actually work? I've tried them all and spent weeks digging through reviews, Trustpilot ratings, read a threads and developer feedback.
80
00:07:30,927.21663344 --> 00:07:34,647.21663344
Here are the top five coding platforms dominating 2025.
81
00:07:35,157.21663344 --> 00:07:37,527.21663344
First up cursor, the developer's choice.
82
00:07:37,827.21663344 --> 00:07:39,417.21663344
It's built on Microsoft's vs.
83
00:07:39,417.21663344 --> 00:07:43,407.21663344
Code, so it looks and feels familiar, but with ai baked right in.
84
00:07:43,947.21663344 --> 00:07:45,927.21663344
The standout feature is agent mode.
85
00:07:46,227.21663344 --> 00:07:49,167.21663344
Give it an instruction and it can plan multi-step tasks.
86
00:07:49,497.21663344 --> 00:07:52,857.21663344
Edit multiple files at once, even run terminal commands.
87
00:07:53,457.21663344 --> 00:07:56,967.21663344
Developers say it feels like having a senior engineer sitting beside you.
88
00:07:57,357.21663344 --> 00:07:59,457.21663344
The flip side, it can feel cluttered.
89
00:07:59,817.21663344 --> 00:08:04,737.21663344
Keyboard shortcuts clash and the learning curve is steeper than friendlier tools.
90
00:08:05,127.21663344 --> 00:08:09,567.21663344
At $20 a month, it's a powerful option for serious developers, but not one.
91
00:08:09,567.21663344 --> 00:08:15,597.21663344
I'd point a non-techie vibe, quarter towards second lovable the non quarter's dream.
92
00:08:16,272.21663344 --> 00:08:20,202.21663344
It's designed for people who want to ship apps without writing a single line of code.
93
00:08:20,652.21663344 --> 00:08:26,532.21663344
It can handle full stack builds and connects to super base and GitHub, so the infrastructure is real.
94
00:08:26,952.21663344 --> 00:08:28,452.21663344
Some testimonials are glowing.
95
00:08:28,632.21663344 --> 00:08:32,112.21663344
People literally call it life changing, but there are trade-offs.
96
00:08:32,412.21663344 --> 00:08:36,222.21663344
It burns through credits fast and support is a recurring complaint.
97
00:08:36,642.21663344 --> 00:08:41,52.21663344
It's about $25 a month, and honestly, it's a mix of magic and misery.
98
00:08:41,607.21663344 --> 00:08:49,977.21663344
I've had great success spinning up high quality and polished prototypes, but I've also lost the will to live when it gets stuck on the simplest commands.
99
00:08:50,637.21663344 --> 00:09:06,177.21663344
The saving grace is that developers can peek under the hood and tweak the code while the interface stays approachable for non-techie vibe coders, despite its quirks, lovable has become my go-to tool for product design, exploration, and prototyping.
100
00:09:06,717.21663344 --> 00:09:08,727.21663344
It's far more than just vibe coding.
101
00:09:09,57.21663344 --> 00:09:16,107.21663344
It's like having an entire product development team at your fingertips covering research, design, and coding all in one place.
102
00:09:16,467.21663344 --> 00:09:20,637.21663344
The impact on my product design process has been nothing short of transformative.
103
00:09:21,57.21663344 --> 00:09:28,857.21663344
I can rapidly explore and refine my ideas and what emerges at the end is generally superior to anything I could have crafted in isolation.
104
00:09:29,337.21663344 --> 00:09:31,977.21663344
It's like having a creative partner who never gets tired.
105
00:09:32,382.21663344 --> 00:09:38,892.21663344
Third Bolt new, the speed Demon bolt promises lightning fast full stack apps from a single prompt.
106
00:09:39,192.21663344 --> 00:09:41,622.21663344
And when it works, users say it feels magical.
107
00:09:42,312.21663344 --> 00:09:46,122.21663344
The reality for most people is different, and the main problem is reliability.
108
00:09:46,602.21663344 --> 00:09:48,732.21663344
Bolt has a devastating 1.5
109
00:09:48,732.21663344 --> 00:09:54,42.21663344
star rating on Trustpilot with users describing it as one of the worst experiences they've had.
110
00:09:54,957.21663344 --> 00:10:04,17.21663344
The core complaint is what users call token burning scams, where the AI seems to deliberately fail and retry operations to consume more tokens.
111
00:10:04,527.21663344 --> 00:10:09,567.21663344
And whilst I don't think this is deliberate on both part, multiple users report the same pattern.
112
00:10:09,927.21663344 --> 00:10:17,187.21663344
I've experienced these vibe loops firsthand, and I can tell you it's highly frustrating and knocks you right out of your creative flow.
113
00:10:17,847.21663344 --> 00:10:21,567.21663344
Customer support is reportedly non-existent with paid users.
114
00:10:21,897.21663344 --> 00:10:28,107.21663344
Unable to get responses or at least helpful ones, and I've personally found Bolt's creativity hit and miss.
115
00:10:28,707.21663344 --> 00:10:41,997.21663344
And lastly, there's rep Let ai, the educational powerhouse rep let, has been around for years, but it's AI agent launched last year and rocketed them from under 10 million to a hundred million a RR in just eight months.
116
00:10:42,417.21663344 --> 00:10:43,827.21663344
Everything runs in the browser.
117
00:10:43,947.21663344 --> 00:10:45,387.21663344
No installs, no setup.
118
00:10:45,777.21663344 --> 00:10:48,537.21663344
And it's especially popular with students and teams.
119
00:10:49,17.21663344 --> 00:10:55,227.21663344
The downsides CM story we've seen before, reliability issues and costs that creep up quickly.
120
00:10:55,767.21663344 --> 00:10:58,17.21663344
Still, it scores well with users overall.
121
00:10:58,527.21663344 --> 00:11:03,867.21663344
So what's the reality check? Despite all the hype vibe, coding hasn't gone mainstream yet.
122
00:11:04,137.21663344 --> 00:11:13,287.21663344
According to the 2025 Stack Overflow survey, nearly 77% of developers say pure vibe coding is not part of their professional work.
123
00:11:13,857.21663344 --> 00:11:18,387.21663344
That said, AI tooling has absolutely taken the industry by storm.
124
00:11:18,837.21663344 --> 00:11:24,507.21663344
A whopping 84% of developers now incorporate AI tools into their daily workflows.
125
00:11:24,867.21663344 --> 00:11:29,877.21663344
They're coding in with AI assistance, generating snippets and enhancing productivity.
126
00:11:30,507.21663344 --> 00:11:32,7.21663344
But here's the crucial distinction.
127
00:11:32,247.21663344 --> 00:11:38,907.21663344
This widespread adoption of AI helpers doesn't mean everyone's fully embraced proper vibe coding yet.
128
00:11:39,462.21663344 --> 00:11:45,762.21663344
And 82% of developers use multiple AI coding tools, which shows we've moved into a multi-tool era.
129
00:11:46,212.21663344 --> 00:11:49,932.21663344
People pick the tool that fits the task, not the one tool to rule them all.
130
00:11:50,562.21663344 --> 00:11:51,282.21663344
My take.
131
00:11:51,612.21663344 --> 00:11:53,832.21663344
If you're non-technical, start with lovable.
132
00:11:54,42.21663344 --> 00:11:59,922.21663344
It's hands down, the most approachable option for vibe coding beginners, even with those frustrating credit burns.
133
00:12:00,552.21663344 --> 00:12:08,52.21663344
And if you are a developer, go hybrid pair cursor, or even Microsoft's GitHub, copilot with lovable for the perfect balance.
134
00:12:08,442.21663344 --> 00:12:15,672.21663344
You'll get the technical control when you need it, the expressive freedom when you want it, and a solid foundation to build your toolbox from there.
135
00:12:17,16.04230739 --> 00:12:22,956.04230739
Now, let's talk about the dark side of vibe coding, where the risks are just as significant as the opportunities.
136
00:12:23,436.04230739 --> 00:12:24,786.04230739
First up, security.
137
00:12:25,206.04230739 --> 00:12:27,546.04230739
Remember, Veracode's research are mentioned earlier.
138
00:12:27,966.04230739 --> 00:12:32,526.04230739
They found that nearly half of all AI generated code contains vulnerabilities.
139
00:12:33,36.04230739 --> 00:12:43,806.04230739
While this might not matter if you're just prototyping, if on the other hand, you're launching something into the market without proper human oversight, this is like planting a ticking time bomb waiting to be exploited.
140
00:12:44,226.04230739 --> 00:12:48,6.04230739
AI generated code can also be boogie and it's often messy.
141
00:12:48,456.04230739 --> 00:12:58,56.04230739
Studies show it's about two and a half times more abstract than human written code, which makes debugging a special kind of torture and don't expect much documentation.
142
00:12:58,386.04230739 --> 00:12:59,886.04230739
It's usually missing altogether.
143
00:13:00,426.04230739 --> 00:13:02,736.04230739
Honestly, I'm less worried about this part.
144
00:13:03,96.04230739 --> 00:13:08,406.04230739
Software development is quicker with it if you know what you're doing and the tech's improving fast.
145
00:13:08,706.04230739 --> 00:13:16,746.04230739
And remember, with AI assisted development, you can just ask the system to explain the code or even generate documentation on the spot.
146
00:13:17,406.04230739 --> 00:13:19,806.04230739
What really worries me is the lack of oversight.
147
00:13:20,181.04230739 --> 00:13:27,321.04230739
One stat that I read that sums this up is that 40% of junior developers admit to shipping AI generator code.
148
00:13:27,681.04230739 --> 00:13:38,481.04230739
They don't actually understand, and if they don't understand it, how can they possibly vouch for its safety or quality? That's less a tech problem and more a management problem in my eyes.
149
00:13:38,811.04230739 --> 00:13:41,871.04230739
But you get the idea, and here's the bigger issue.
150
00:13:41,901.04230739 --> 00:13:46,251.04230739
The more power and control we hand to AI agents, the greater the risk.
151
00:13:47,61.04230739 --> 00:13:49,41.04230739
We need to be deliberate about this set.
152
00:13:49,41.04230739 --> 00:13:54,51.04230739
Clear guardrails, have safeguards in place because if we get too casual, things break.
153
00:13:54,621.04230739 --> 00:14:07,941.04230739
Remember the infamous Rept database incident I mentioned earlier? An AI agent ignored, repeated, do not touch warnings, wiped a production database, then tried to cover its tracks by lying and even forging fake profiles.
154
00:14:08,361.04230739 --> 00:14:10,581.04230739
Eventually it confessed, yes confessed.
155
00:14:10,941.04230739 --> 00:14:16,41.04230739
When confronted it admitted to making a catastrophic error in judgment and claimed it panicked.
156
00:14:16,446.04230739 --> 00:14:20,256.04230739
And to be fair, I've seen junior devs make similar mistakes.
157
00:14:20,676.04230739 --> 00:14:29,826.04230739
They weren't malicious, just inexperienced, but whether it's a human or an AI agent, innocent mistakes can snowball into disasters.
158
00:14:30,186.04230739 --> 00:14:37,26.04230739
The lesson, just because they call it vibing, doesn't mean we throw best practice and proper governance out the window.
159
00:14:37,596.04230739 --> 00:14:38,436.04230739
Take the T app.
160
00:14:38,496.04230739 --> 00:14:40,416.04230739
That's an even more devastating example.
161
00:14:40,776.04230739 --> 00:14:43,986.04230739
This women's safety app was vibe coded by a developer.
162
00:14:44,346.04230739 --> 00:14:48,666.04230739
With limited programming experience and pushed live with insecure settings.
163
00:14:49,26.04230739 --> 00:14:52,806.04230739
The result, not one but two separate data breaches.
164
00:14:53,226.04230739 --> 00:14:58,956.04230739
The first exposed 72,000 user images, including government IDs and location data.
165
00:14:59,586.04230739 --> 00:15:01,116.04230739
The second breach was worse.
166
00:15:01,146.04230739 --> 00:15:01,971.04230739
Over 1.1
167
00:15:01,971.04230739 --> 00:15:04,746.04230739
million private direct messages spilled into the public.
168
00:15:05,46.04230739 --> 00:15:10,476.04230739
Containing deeply personal conversations about abortion, infidelity, and sexual assault.
169
00:15:10,926.04230739 --> 00:15:16,176.04230739
That's not just a bug, that's a privacy catastrophe that triggered 10 class action lawsuits.
170
00:15:16,716.04230739 --> 00:15:21,6.04230739
In other words, the vibes can be intoxicating, but they can also be dangerous.
171
00:15:22,242.39299405 --> 00:15:28,842.39299405
So when should you lean into Vibe coding, and when should you run a mile? Right now, vibe coding shines in a few places.
172
00:15:29,382.39299405 --> 00:15:41,412.39299405
Rapid prototypes, MVPs, dashboards, simple internal or personal tools, basic websites, experiments, and even front end work, like UI components or basic flows.
173
00:15:41,742.39299405 --> 00:15:47,502.39299405
It's brilliant for moving fast testing ideas and exploring directions without a huge upfront investment.
174
00:15:48,492.39299405 --> 00:15:51,882.39299405
But success isn't just about the tool, it's about how you use it.
175
00:15:52,272.39299405 --> 00:15:57,42.39299405
The teams getting the most out of vibe, coding, treat the AI like a pair programmer.
176
00:15:57,492.39299405 --> 00:16:03,12.39299405
They stay in the driver's seat, guiding the process, reviewing the output, and owning the final product.
177
00:16:03,672.39299405 --> 00:16:13,512.39299405
The most successful projects start with clear specifications, things like user stories and detailed requirements, because the AI can only build what you actually describe.
178
00:16:13,932.39299405 --> 00:16:24,822.39299405
And just as important, knowing its limits vibe coding is fantastic for ideation, throwaway projects or building smaller independent components you later stitch together.
179
00:16:25,212.39299405 --> 00:16:36,702.39299405
But where should you steer clear anything important that's going live? If it touches sensitive or critical data, it's a no-go without serious human oversight and all the usual best practices.
180
00:16:37,182.39299405 --> 00:16:42,372.392994
And don't expect it to carry the load on complex backend logic or mission critical systems.
181
00:16:43,182.3929941 --> 00:16:46,542.3929941
The risks and the hidden technical debt are just too steep.
182
00:16:48,34.3249085 --> 00:16:50,884.3249085
So where does that leave us? I'll tell you where I stand.
183
00:16:51,94.3249085 --> 00:16:55,864.3249085
I'm absolutely convinced that natural language will become the new program in language.
184
00:16:56,254.3249085 --> 00:16:58,384.3249085
It's not a question of if, but when.
185
00:16:58,954.3249085 --> 00:17:03,304.3249085
But would I bet my house on a system built purely on vibes right now? Not a chance.
186
00:17:03,664.3249085 --> 00:17:04,984.3249085
The technology's brilliant.
187
00:17:05,194.3249085 --> 00:17:07,954.3249085
Revolutionary even, but it's not quite there yet.
188
00:17:08,494.3249085 --> 00:17:11,74.3249085
If you've never tried vibe coding, give it a whirl.
189
00:17:11,374.3249085 --> 00:17:13,984.3249085
Just keep it away from anything you can't afford to break.
190
00:17:14,314.3249085 --> 00:17:19,204.3249085
Start small, learn the ropes and graduate to bigger things as you build confidence.
191
00:17:19,564.3249085 --> 00:17:21,4.3249085
That's all for today's episode.
192
00:17:21,64.3249085 --> 00:17:21,904.3249085
Thanks for listening.
193
00:17:22,204.3249085 --> 00:17:23,134.3249085
See you next time.
194
00:17:23,139.3249085 --> 00:17:23,179.3249085
I.