Overview

Before you start

A few things to know before Phase 0 — how to use this, what you actually need, and two accounts to set up early.

How this works

Do the steps in order. Each one builds on the last, so skipping ahead usually backfires. For every phase: watch the main video first, type the code out yourself instead of copying it, then build the small project at the end. That last part is where the learning actually happens.

You’ll feel lost sometimes. That’s normal, and it doesn’t mean you’re not cut out for this. It means you’re learning something hard. Everyone who codes has felt it, and most still do.

About how long this takes: realistically a year and a half to three years, depending on how much time you put in. You don’t wait that long to see results — you’ll have a website online in about six months and a full app in about a year. An hour most days beats a long weekend once a month.
You don’t need a powerful computer. An old laptop is fine all the way through. If all you have is a phone, you can still write and run real code in the browser with Replit (replit.com) or Google Colab (colab.research.google.com). No excuse to wait.

Two accounts to set up early

They’re free, take ten minutes, and end up mattering more than any certificate when you’re looking for work.

GitHub

where your code lives online

Every project you build goes here, and over time it becomes the proof that you can actually code. When you apply for a job or a freelance gig, people look at your GitHub before anything else — it shows what you’ve built, not just what you claim.

LinkedIn

where you’re found for work

This is where recruiters and clients look for developers. A simple, honest profile — what you’re learning, the projects you’ve shipped, a link to your GitHub — is enough to start. Most early opportunities come from someone seeing your work here, not from sending CVs into the void.

Frontend, backend, and database and how they talk
The three parts of a website, and how they talk to each other.
Start at Phase 0 →