Courses¶
Overview¶
Structured courses accelerate foundations with exercises and projects. Mix MOOCs, university offerings, and vendor trainings depending on your gaps.
Why This Exists¶
Self-study benefits from pacing and assessments; courses supply both when chosen intentionally.
Suggested directions¶
| Area | Examples | Notes |
|---|---|---|
| CS foundations | OS, compilers, distributed systems MOOCs | Pair with small projects |
| Databases | CMU 15-445 materials | Labs are excellent if you do them |
| ML / AI | Stanford CS229/CS224N (public materials) | Math-heavy; schedule accordingly |
| System design | Paid platforms with mock interviews | Practice explaining out loud |
Key Concepts¶
Projects over certificates
Hiring loops value artifacts you can discuss; prioritize courses that produce code or designs you own.
Code Examples¶
- Watch lectures at 1x for hard sections only
- Complete >= 70% assignments
- Publish one portfolio writeup tying course to a personal project
Interview Questions¶
How do you list courses on a resume?
If substantial and recent, under Education or Projects with outcomes—not as filler buzzwords.
Practice Problems¶
- Align a course project with a GitHub repo README that explains architecture
- After each unit, add five flashcards for definitions you would struggle to recall
Resources¶
- MIT OpenCourseWare
- Coursera / edX — audit options vary