Self-Taught to Intern: What Actually Helped

I started learning to code at 19 with a YouTube tutorial on HTML. Eight months later I landed my first frontend internship. No degree, no bootcamp, no connections. Here's an honest account of what actually moved the needle.

What I Got Wrong First

The first 6 months I basically just watched tutorials. I'd watch someone build a to-do app, feel like I understood it, then try to build something and freeze completely.

Tutorial hell is real. You feel productive but you're not learning — you're pattern-matching. The moment you have to make a decision the tutorial didn't cover, you're stuck.

The Shift That Changed Everything

I stopped asking "what should I learn?" and started asking "what do I want to build?"

I wanted to build a Discord bot for my friend group. So I learned Node.js to build it. I wanted to store settings across restarts, so I learned SQLite. The bot got slow, so I learned basic caching. The bot had downtime, so I learned how to run it on a cheap VPS and keep it alive with pm2.

That one project taught me more than 6 months of tutorials. And at the end I had something real I had built and used every day.

What I'd Actually Recommend

1. Build things that itch you. Not tutorial projects. Things you actually want to exist. The motivation difference is enormous.

2. Read code obsessively. Pick a library you use. Open its source on GitHub. Start from the entry point and follow the breadcrumbs. This is how you learn what "good code" looks like.

3. Solve real problems on the internet. Find an open GitHub issue in a project you use. Even just reading the discussion teaches you how engineers think. When you can close one, do it.

4. Write about what you learn. Not for an audience — for yourself. Explaining something forces you to understand it. I kept a private Obsidian doc of things I learned each week. Reviewing it months later was like finding buried treasure.

5. Get early feedback. Share your code with someone more experienced, even in a Discord server. One critical code review taught me more about clean code than two months of reading books.

On the Internship Application

When I applied, my GitHub had maybe 15 projects. Most were small. But they were real — things I actually built for a reason, not "Todo App Tutorial CRUD".

In my interview, they asked me to walk through a project I was proud of. I talked about the Discord bot and the problems I'd solved. They didn't care that I didn't have a degree. They cared that I could think through a problem and had actually shipped something.

The Uncomfortable Truth

There's no shortcut. The self-taught path takes longer than a CS degree in some ways, and shorter in others. You'll spend a lot of time feeling lost and stupid. That feeling is the learning.

The people who make it are not the ones who are naturally talented — they're the ones who kept building things when it felt pointless. Keep building.