I didn’t major in computer science. I never went to a coding boot camp. And until recently, I thought “backend” was something you only worried about at the gym.
But in 200 hours — with no prior experience and nothing but a stubborn will and access to ChatGPT, Copilot, and a stack of YouTube tutorials — I built a functioning, usable web product.
Part 1: The Big Mental Unlock — You Don’t Need to Know Everything
I started with a vague product idea: something like a habit tracker but layered with social features and AI nudges.
In the old world, I would’ve needed:
- A designer
- A front-end dev
- A back-end dev
- A project manager
- A whole lot of VC funding
Today, with AI copilots and low-code tools? You can stumble your way into MVP territory. What finally clicked for me was this:
I didn’t need to learn “web development” in the academic sense. I needed to learn just enough to ask good questions.
Once I started treating ChatGPT like a senior dev, things shifted. I’d say:
Here’s what I want the feature to do. Can you generate the HTML and JS
It would respond. Sometimes it broke. Sometimes it hallucinated. But I learned faster by fixing it than by reading blog posts for hours.
Part 2: The Stack That Worked for Me
Here’s what I ended up using:
- Frontend: React + Tailwind CSS (with ChatGPT writing 80% of the boilerplate)
- Backend: Supabase (PostgreSQL + Auth + Storage = no-brainer)
- AI: OpenAI API to give users natural-language feedback
- Deployment: Vercel (simple, fast, forgiving)
- Project Planning: Notion + Pen and Paper
I didn’t “master” any of these tools. I treated each one like a Lego brick, and AI was the instruction manual whispering steps into my ear.
Part 3: The 200 Hours — What That Looks Like
Let’s be real: 200 hours is a LOT when you don’t know what you’re doing.
Here’s roughly how it broke down:
- 40 hours: Watching videos + absorbing tech concepts
- 60 hours: Building UI, smashing bugs, starting over
- 30 hours: Backend setup, crying over auth tokens
- 20 hours: AI integrations + testing
- 50 hours: Iteration, debugging, late-night panic Googling
Some days I felt unstoppable. Others I wanted to quit. But every day, I built momentum. And momentum beats motivation.
Part 4: The Hardest Truth — AI Doesn’t Make It “Easy”
Here’s the trap most people fall into:
They think AI = effortless. The reality?
AI gives you power, but only if you’re willing to fail faster.
You have to:
- Ask better questions.
- Get good at describing problems.
- Know when to take a break before rage-deploying broken code.
AI can’t teach you patience. But it rewards it.
Part 5: Why This Changes Everything for Beginners
Here’s what I want to scream from the rooftops:
If you have a product idea, you no longer have to wait for someone else to build it.
You can start. You can learn by doing. You can fail and still ship something that works. 200 hours used to barely scratch the surface of “becoming a developer.” Today? With the right tools and mindset, it’s enough to go from zero to something real.
You’re Allowed to Build Before You Feel Ready
I wasn’t ready. I still feel like I’m winging it. But I’m not just consuming anymore. I’m creating. And if you’re reading this wondering if you could do it too? You already have what it takes. You just haven’t hit “Start” yet.
No comments:
Post a Comment