Curriculum & Learning
Questions about what you'll learn, how the curriculum is structured, and our project-based learning approach.
Five tracks covering the full spectrum: Foundation (CS fundamentals, data structures, algorithms), Web Engineering (frontend, backend, databases, APIs), Systems (architecture, performance, security), Professional Engineering (Git, testing, CI/CD, debugging), and a Capstone project. 35 modules total, 256 lessons.
Every module ends with a hands-on project. Examples: a memory visualizer, a full-stack web application, a REST API, a CI/CD pipeline, and a production capstone app. These aren't toy exercises — they're portfolio-worthy projects that demonstrate real engineering skills to employers.
The Foundation track should come first if you're coming from a pure vibe coding background. After that, Web Engineering is recommended next, but you can jump into Systems or Professional Engineering if you have some background. The Capstone should be last — it draws from all other tracks.
Three types: Interactive exercises (write and run code in the browser), Animated visualizations (see how data structures and algorithms work step-by-step), and Reading modules (deep explanations with examples). Each lesson is 15-25 minutes. No lecture videos, no talking heads.
We apply 20 evidence-based learning principles including spaced repetition, interleaving, retrieval practice, and the generation effect. In practice, this means you're constantly tested on what you've learned, concepts from different modules are mixed together, and you generate solutions rather than recognize them.
Yes. The Foundation track covers data structures and algorithms at interview-ready depth. The Systems track includes system design fundamentals. The Professional Engineering track covers the collaboration and debugging skills tested in pair programming rounds. We don't teach 'interview tricks' — we teach actual engineering, which is better preparation.