Road Mates EnterHow to become a Web Developer, phase by phase: what you do in each one, how long it takes, and the proof that shows you're done.
6 phases1–2.5 years15 resources
Working through structured tutorials and exercises to learn markup, styling, layout, and core JavaScript, plus Git and the browser dev tools. By the end, the person can hand-build a responsive static page and add basic interactivity without copying code line by line.
You're done when you can show
A GitHub repo with a hand-coded responsive page deployed to a live URL.
Resources
Stopping guided courses and building their own small apps from a blank folder: a to-do app, an API-driven dashboard, a clone of a familiar site. They learn a framework such as React and fetch data from public APIs, debugging on their own and reading documentation instead of following videos.
You're done when you can show
Three self-designed projects live online with source code on GitHub.
Resources
Adding a backend, a database, authentication, and deployment to build one substantial app that real people can sign up for and use. This phase produces a production-grade project with tests, environment configuration, and a readable README.
You're done when you can show
Live URL of a full-stack app with user accounts and a public repo.
Resources
Moving from solo projects to code other people depend on: contributing to open-source repos, doing freelance sites for small clients, or volunteering for nonprofits. The person learns code review, pull request etiquette, and working within existing conventions and deadlines.
You're done when you can show
Merged pull requests on someone else's repo or a paid client site that is live.
Resources
Polishing a portfolio site and resume, sending targeted applications, networking, and practicing technical interviews and take-home assignments. The phase ends with an accepted offer for a paid web developer position.
You're done when you can show
A signed offer letter or contract for a web developer role.
Resources
Shipping tickets in a team's codebase, owning features from spec to deployment, fixing bugs, and responding to code review. Over time the person takes on larger features independently and learns performance, accessibility, and testing practices on the job.
You're done when you can show
A feature you owned that is live in production, cited in a performance review.
Resources
Walk this road with people on it.
Track each phase, post your proofs, and get matched with people in the same phase.