codebuddy.tech

From GPT to Claude: A Vancouver Developer's Journey Through the Wild West of Vibe Coding

Six months ago, I thought I'd found the holy grail. GPT was going to change everything. But here's the thing about revolutionary moments: sometimes you don't realize how clunky your revolution was until you find something better.

Enter Anthropic, the company founded by former OpenAI employees, and Claude, their flagship model. Working with Claude made me realize that my early GPT days were like trying to code on a 1990s Nokia compared to an iPhone.

What the Hell is Vibe Coding?

The term was popularized by Andrej Karpathy, who described it as fully leaning into the vibes, letting the AI generate code, and just taking it for granted. It sounds liberating. It is liberating. But it's also fragile.

Here's the beautiful paradox: you don't need to know anything about code to start vibe coding. What you need is belief in yourself and zero fear. No computer science degree, no bootcamp certificates. Just vibes.

But here's the contrarian truth: zero fear quickly becomes zero understanding. When the AI produces a bug, you have no mental model to diagnose it. Vibe coding without foundational knowledge is like driving a Tesla with autopilot in a blizzard — you'll feel brilliant until you hit black ice.

The Open Source Revolution

I can run a command that pulls code from some developer's server — maybe they're in Estonia, maybe they're in their mom's basement in Ohio — and boom, that code downloads to my machine. This is the modern miracle of open source.

The catch? Building is the easy part. Distribution — getting your creation in front of people who actually want to use it — that's the real challenge. The internet is littered with brilliant projects that nobody knows exist.

Why Claude Changed Everything For Me

GPT felt like having a smart intern who sometimes gave brilliant insights and sometimes confidently told you that Paris was the capital of Italy. Claude feels different. More reliable. It's like the difference between a friend who's always game for your crazy schemes and a friend who's game but also asks thoughtful questions that make you realize maybe you should wear a helmet.

When I'm vibe coding with Claude, I spend less time debugging AI-generated nonsense and more time actually building. The code tends to be more maintainable, better documented, and follows actual best practices.

The Dark Side of the Vibe

Vibe coding has created a generation of developers who can ship products but can't maintain them. Who can build features but can't optimize them. I've seen brilliant non-technical founders build impressive MVPs through pure vibe coding, then hit a wall when they need to scale.

This isn't meant to scare you — it's meant to keep you grounded. Vibe coding is a superpower, but like any superpower, it comes with responsibility.

Building Between Rides

Here's the thing about building AI products between Uber rides: constraints breed creativity. When you have 15 minutes between dropping someone off in Burnaby and picking someone up in Richmond, you learn to make every prompt count.

Some of my best ideas have come while stuck in bridge traffic, frantically typing prompts into Claude on my phone, hoping to capture an insight before my next passenger gets in the car.

Embrace the Vibe, Respect the Craft

After six months of vibe coding, bouncing between GPT and Claude, building products between Uber rides in Vancouver traffic, here's what I've learned: this technology is simultaneously more powerful and more fragile than the hype suggests.

Vibe coding will democratize software creation in ways we're only beginning to understand. But it won't eliminate the need for deep technical understanding — it will make that understanding more valuable, not less.

So dive in. Start vibe coding. Build ridiculous things. Break stuff. Ship products that probably shouldn't work but somehow do. But stay curious about why they work. The future belongs to the vibe coders who never stop learning.