Why I Chose Web Development - Without a CS Degree

The Honest Beginning

I didn't wake up one day with a vision of becoming a developer. It started with a practical problem: I wanted to build something, and I didn't want to pay someone else to build it for me.

That first "something" was a simple webpage. Nothing impressive. But the moment it appeared in the browser - actually worked - something clicked.

Why Not a Computer Science Degree?

I'll be honest about this. A CS degree would have taught me a lot. But I was already learning, already building, and the cost of stopping to spend four years in a classroom didn't add up for me at that point.

So I chose the harder path: learning without a curriculum, without a professor grading my work, without deadlines except the ones I set myself.

How I Actually Learned

There's no secret method. I picked a technology (HTML, then CSS, then JavaScript), built something with it until I hit a wall, figured out why the wall was there, and moved forward.

The progression that worked for me:

1. HTML & CSS - Understanding structure and presentation
2. JavaScript - Making things interactive
3. React - Component-based thinking
4. Next.js - Server-side rendering, routing, full-stack capabilities
5. TypeScript - Type safety and better code quality
6. SEO & Performance - Making what I built actually discoverable and fast

Each step felt overwhelming at first. That feeling never fully goes away - it just becomes familiar.

What Kept Me Going

Curiosity. Genuinely. When something doesn't work, I want to know why. Not because I have to, but because not knowing bothers me more than the discomfort of figuring it out.

That mindset - treating bugs as puzzles rather than failures - made a significant difference in how I progressed.

What I've Built

Real things. A salon website with local SEO optimization. A mentoring platform. A blog CMS. An AI-assisted portfolio. None of these are side projects that live in a GitHub folder - they're live, they're used, and they taught me more than any tutorial could.

What Self-Taught Actually Means

It means you fill your own gaps. Nobody tells you what you don't know. Nobody catches your bad habits early. You have to develop judgment about what good code looks like before you've seen enough of it to know.

It also means you're never done. There's always something else to learn, some pattern to understand better, some tool to evaluate.

I consider that a feature, not a bug.

For Anyone Considering the Same Path

Start building before you feel ready. You'll never feel ready. The only thing that actually teaches you is building something that has to work - for a real user, in a real browser, on a real device.

The discomfort of not knowing is temporary. The skill you build by pushing through it stays.

If you want to follow the journey: I write about what I'm building and learning here on this blog.