A programming curriculum where you build the solutions yourself.
Self-paced programming curricula that take you from zero to job-ready. No hand-holding. No copy-paste answers. You struggle, you learn, you build.
Current track: Full-Stack React (48 weeks)
Target: Career changers with 1-2 hours daily Outcome: Job-ready full-stack developer with a portfolio of deployed projects
You don't understand something until you've built it from scratch. In this curriculum, you'll recreate: array methods, promises, event emitters, React hooks, a query builder, an ORM, and more.
Labs describe the problem. You discover the answer. This mirrors real-world development where Stack Overflow won't have your exact solution.
Every time you want to quit, you're about to level up. We don't remove the difficulty—we prepare you for it.
| Module | Duration | Topics |
|---|---|---|
| Environment & Tools | 2 weeks | Terminal, VS Code, Git |
| Programming Fundamentals | 8 weeks | Logic, functions, data structures |
| JavaScript & Web Basics | 6 weeks | ES6+, async/await, DOM, HTML/CSS |
| TypeScript | 4 weeks | Types, generics, real-world patterns |
| React | 10 weeks | Components, hooks, Server Components, testing |
| Backend & PostgreSQL | 10 weeks | Node/Express, SQL, API development, Prisma |
| Full-Stack Capstone | 8 weeks | Complete application, deployment |
By the end, you'll have:
- 5+ deployed projects (not localhost screenshots—real URLs)
- Custom implementations of core programming concepts
- A full-stack application with auth, database, and production deployment
- A GitHub profile that tells your story through commits
- CLI Calculator, Number Guessing Game, Todo List
myMap(),myFilter(),myReduce()- Promise implementation with
.then()and.catch() - Event Emitter with pub/sub pattern
- Type-safe Event Emitter (generics)
- Typed Fetch Wrapper
- Custom React Hooks (
useLocalStorage,useFetch,useDebounce) - Accessible Component Library
- SQL Query Builder
- Simple ORM
- Full-Stack Capstone (your choice of project)
Yes:
- Career changers willing to commit 1-2 hours daily for ~12 months
- People who want to actually understand code, not just copy it
- Self-motivated learners who can push through frustration
No:
- People looking for quick wins or shortcuts
- Those who need constant hand-holding
- Anyone who wants to "learn to code in 30 days"
- Read
Course.mdfor the full overview - Start with Module -1: Before You Begin
- Bookmark the When You're Stuck guide
no-solutions/
├── Course.md # Start here
├── full-stack-react/ # The curriculum track
│ ├── module--1-before-you-begin.md
│ ├── module-0-environment-tools.md
│ ├── module-1-programming-fundamentals.md
│ ├── module-2-javascript-web-basics.md
│ ├── module-3-typescript.md
│ ├── module-4-react-typescript.md
│ ├── module-5-backend-postgresql.md
│ └── module-6-fullstack-capstone.md
├── guides/ # Support resources
│ ├── when-youre-stuck.md
│ ├── troubleshooting.md
│ ├── concept-diagrams.md
│ └── using-ai-to-learn.md
├── CLAUDE.md # AI teaching mode instructions
└── .cursorrules # Cursor AI instructions
This is the first track. More are coming.
- Full-Stack React — JavaScript, TypeScript, React, Node.js, PostgreSQL
- Python & Data Science — Python fundamentals, pandas, data analysis, ML basics
- Mobile Development — React Native, cross-platform apps
- DevOps Fundamentals — Linux, Docker, CI/CD, cloud deployment
- Computer Science Core — Algorithms, data structures, system design
Want to see a specific track? Open an issue.
This curriculum is configured for AI coding assistants (Claude, Cursor, Copilot). When you use AI in this repository, it automatically switches to teaching mode:
- Asks what you've tried before helping
- Gives hints, not answers
- Guides you to discover solutions yourself
Because a developer who can only code with AI assistance isn't really a developer.
This curriculum is opinionated by design. If you have suggestions:
- Found an error? Open an issue
- Have a better explanation? PRs welcome for clarity improvements
- Want to add solutions? No. That's the point.
MIT — Use it, fork it, teach with it. Just don't add the solutions.
"The master has failed more times than the beginner has tried."
Every developer you admire was once mass console.log-ing to figure out why their code didn't work. They got through it. So will you.
The path is clear. The work is yours.