What Happens When You Type a URL and Press Enter
DNS lookups, TCP and TLS handshakes, HTTP requests, servers, and the browser's rendering pipeline. The whole journey of a web page, explained so it finally clicks.
Read →The Full Stack Developer Roadmap: What to Learn, in What Order
A practical, no-hype learning path from your first HTML page to deploying real full stack apps. What to learn at each stage, what to skip for now, and the project that proves you're ready.
Roadmaps online tend to look like subway maps of an entire city: hundreds of technologies, arrows everywhere, no clear starting point. That's overwhelming and mostly unnecessary. You don't need to learn everything. You need to learn the right things in an order where each step builds on the last.
Here's a roadmap that stays useful even as specific frameworks come and go.
Stage 1: the foundations of the web
Learn: HTML, CSS and how the web works.
- Semantic HTML: headings, lists, forms, buttons, links. (Why semantics matter for accessibility.)
- CSS layout with Flexbox and Grid. (Which one to use when.)
- Responsive design. (Mobile-first explained.)
- What happens between typing a URL and seeing a page. (The request journey.)
Prove it: build a multi-page personal site that looks good on a phone, without a framework.
Stage 2: JavaScript, properly
Learn: the language itself before any framework.
- Variables, functions, arrays, objects, loops
- Scope and closures
- The DOM and events
- Promises,
async/awaitandfetch(common async mistakes) - Modules and basic tooling (npm, a bundler or dev server)
Prove it: build an interactive app in plain JavaScript that fetches data from a public API: a weather dashboard, a book search, a quiz. (Why fundamentals first.)
Stage 3: Git and the command line
Learn: enough to work like a professional.
git add,commit,push,pull, branches, merges, pull requests- Undoing mistakes (here's how)
- Basic terminal navigation and commands (Linux basics)
Start using Git from Stage 1 if you can. Everything you build should live in a repository.
Stage 4: a frontend framework
Learn: one popular framework, deeply. React, Vue, Svelte and Angular are all valid choices; React has the largest job market in many regions, but the concepts transfer.
- Components, props and state
- Effects and data fetching (useEffect pitfalls)
- Routing and forms
- State management basics (choosing the right state tool)
Optionally add TypeScript here. It catches a lot of mistakes and is widely expected. (Is TypeScript worth it?)
Stage 5: the backend
Learn: one server-side language and framework. Node.js with Express or a full stack framework keeps you in JavaScript; Python, PHP, Go, C# or Java are all solid choices too.
- HTTP, routing, middleware and status codes (status codes explained)
- Building a REST API (design best practices)
- Input validation and error handling (validation done right)
- Environment variables and configuration (config hygiene)
Stage 6: databases
Learn: SQL first. It's everywhere and it lasts.
- Tables, relationships and keys
SELECT,INSERT,UPDATE,DELETE, joins (joins explained)- Indexes (indexing basics)
- Migrations and an ORM or query builder (migrations)
Learn a document database later if a project calls for it. (SQL vs NoSQL.)
Stage 7: authentication and security
- Sessions vs tokens (comparison)
- Password hashing, access control, common vulnerabilities (security checklist)
Stage 8: deployment
- Deploying frontend, API and database (for free)
- Domains, DNS and HTTPS
- CI with GitHub Actions (starter guide)
- Optionally Docker (beginner guide)
Stage 9: testing and quality
- Unit, integration and end-to-end tests (which tests to write)
- Code review habits and clean code (clean code tips)
The capstone project
Build one complete app that uses everything: user accounts, a database with relationships, a REST API, a polished frontend, tests for critical paths, and a deployment with CI. Something like a booking system, an expense tracker for groups or a small marketplace.
Then write it up as a case study for your portfolio. (Portfolio tips.)
What to skip (for now)
- Microservices, Kubernetes and complex cloud architecture
- Every new framework that trends for a week
- Advanced algorithms beyond the basics, unless you're preparing for interviews that need them
- Three languages at once
You'll meet those later, and they'll make far more sense once the fundamentals are solid.
How long does it take?
It varies enormously with time available and prior experience. Working consistently part-time, many people reach "can build and deploy a full stack app" in roughly a year. What matters most is building projects at every stage instead of only consuming courses. (Escaping tutorial hell.)
FAQ
What should I learn first to become a full stack developer?
HTML, CSS and JavaScript fundamentals, then Git, a frontend framework, a backend language with SQL, authentication and deployment, in that order.
Do I need a computer science degree?
No. Many full stack developers are self-taught or bootcamp graduates. A strong portfolio of real, deployed projects demonstrates what employers need to see.
Which backend language is best for full stack development?
There's no single best. Node.js lets you use JavaScript everywhere, while Python, PHP, C#, Java and Go all have strong frameworks and job markets. Pick one and go deep.
