The roadmap I'm actually following
Every "learn to code" roadmap looks reasonable until you're the one trying to follow it in order. Here's the tree I'm actually working through, and the reasoning behind the order — not just the list.
The learning tree
C Language Basics
Syntax, control flow, functions
Pointers & memory management
Structures & unions
File handling
↓
C Data Structures
Linked lists, stacks, queues
Sorting algorithms
Searching algorithms
↓
Web Development Intro
Client-server architecture
HTML → CSS → JavaScript
Static website
↓
JavaScript Front-End
React / Angular / Vue.js
Simple UI with a framework
↓
Backend Development
Databases (SQL + NoSQL)
REST APIs
Authentication
↓
Full-Stack Integration
Connect frontend ↔ backend ↔ database
Deploy to cloud
Why C first, when nobody ships a C web app
Because pointers and manual memory management force you to actually understand what a variable is, instead of trusting a garbage collector to make the question irrelevant. Every language I've touched since — Python's references, Rust's ownership model, even JavaScript's closures — makes more sense having done C first. It's the annoying prerequisite that makes everything after it click faster.
Tech stack by layer
| Layer | Technologies |
|---|---|
| Systems / low-level | C, C++, Rust |
| Frontend | HTML, CSS, JavaScript, React, Vue, Angular |
| Backend | Python (Flask/Django), Node.js, Java (Spring), Go |
| Database | MySQL, PostgreSQL, MongoDB, Redis |
| DevOps | Docker, Kubernetes, Jenkins, Ansible |
| AI/ML | TensorFlow, PyTorch, scikit-learn, Ollama, MLX |
| Infra | AWS, Azure, GCP, Heroku |
The order I'm actually following, given what's already in my notes
- C basics
- DSA fundamentals
- Python scripting
- Java / Go / Rust
- HTML/CSS/JS + React
- Node.js
- SQL + MongoDB
- REST APIs
- A basic chatbot (TensorFlow)
- Local LLMs (Ollama + Apple MLX)
- Agentic AI patterns
Steps 9 through 11 are arguably "extra" for a roadmap that's nominally about full-stack web development — but AI-literacy is quickly becoming as core to full-stack as knowing SQL, so I'm not treating it as optional.