Vibe Coding: My 48-Hour Journey
I’m Not a Developer - But I Tried to Build Anyway (with AI as My Copilot)
Let’s get this out of the way: I’m not a developer. It always feels a little awkward to say that, especially since I’ve spent my entire career working in and around technology. But while I’ve never written production code, I’ve spent years obsessing over the why - why certain technology trends gain traction, why others fade, and how those choices shape the future of products, businesses, and even industries.
APIs, cloud computing, data pipelines, generative AI - I’ve followed these shifts with deep curiosity. Not from the perspective of writing code, but from setting product and technology strategy that can scale. Still, I’ve always had a quiet itch to roll up my sleeves and build something with my own hands - keyboard included.
Lately, I’ve been captivated by a new concept: Vibe Coding - the idea that generative AI can make coding feel more like collaborative ideation than technical execution. Just as AI tools help students get past writer’s block, could they do the same for building software?
One morning, that curiosity tipped over into action. I decided to run an experiment: Could I, a non-coder, use AI to build a full-stack application from scratch?
I gave myself 48 hours. No tutorials. No prep. Just me, an idea, and AI.
Step One: Set the Bar Low, Then Build
I downloaded the free version of Cursor - an AI-native code editor I heard about on a podcast. I used only the chat prompt, intentionally avoiding documentation or walkthroughs. My goal wasn’t to learn to code. It was to learn if I could build without knowing how to code.
So, what did I try to build?
I’m a musician in my spare time and have long thought about a platform to connect local musicians with venues—a kind of OpenTable, but for live music. Niche? Sure. But I’m convinced the world needs it.
I typed out my idea in a paragraph. Within seconds, the AI validated the concept (thanks for the ego boost) and returned a development plan:
Frontend: React
Backend: (something I skimmed past)
Database: Postgres
I didn’t fully understand everything, but I recognized enough to say: "Sounds great, let’s go." Kind of like nodding at your mechanic while secretly Googling "transmission vs. alternator."
Watching the Magic (and Madness) Happen
The AI guided me through installing packages, configuring my dev environment, and scaffolding the project. I followed its instructions step by step, clicking “yes” with only mild concern I was giving my laptop away to Skynet.
Then came the wild part: the code. It wrote files, configured routes, initialized a DB, and eventually asked:
“Would you like to run your application?”
I said yes. It compiled. It loaded a URL.
And then - boom.
A working web app. Clean UI. Account login. Working nav. It wasn’t just theoretical - it existed. And for a moment, it felt like touching the future.
And Then... the Doom Spiral
I spotted a small copy issue in the nav bar and asked the AI to fix it.
That was my first mistake.
It made the change - but also:
Resized icons randomly
Stacked content vertically
Broke layout responsiveness
The ‘90s called—they wanted their GeoCities design back.
I stayed true to the experiment and kept using only the chat function, trying to describe the issue in different ways. Each time, the AI "fixed" something… but the app got worse. It was like playing Jenga in reverse.
Eventually, I hit the free trial limit.
No fixes. No rollback. No way forward.
What I Learned...
This experience left me with two competing emotions:
Amazement: We're so close to a world where anyone with an idea can build software. I got further in 48 hours than I thought possible—without writing a single line of code myself.
Reality Check: We’re not there yet. For non-developers, the debugging experience still feels like shouting into the void. One wrong prompt and you’re in CSS purgatory.
But I’m optimistic. In fact, I’m energized. I’ll try again soon—maybe with a paid plan, maybe with a little more technical context.
In the meantime, to all the real engineers out there: I’ve always respected your craft. After this? That respect has doubled.
I can’t wait to try again in a few months.
