Computer Architecture¶
Track position¶
ISAs, pipelines, caches, parallelism, and performance analysis for understanding how hardware executes programs.
Recommended prerequisite tracks¶
Suggested order¶
Courses¶
| Course | Institution | Role | Tier | Practice coverage |
|---|---|---|---|---|
| Computer Architecture | Cornell University | Mainline | A | Complete |
| Build a Modern Computer from First Principles: From Nand to Tetris, Part II | Hebrew University of Jerusalem | Alternative | S | Complete |
| Computer System Architecture | MIT | Alternative | A | Partial |
| Great Ideas in Computer Architecture | University of California, Berkeley | Alternative | A | Complete |
| Operating System Engineering | MIT | Alternative | A | Complete |
How to choose¶
- For a first systematic pass, start with audit-passed mainline courses; read the limitation before using a record marked “Audit review,” and rarely take parallel alternatives.
- Tiers measure public-resource completeness and self-study executability, not institutional or instructor prestige.
- Use supplements only to close a specific topic, tool, or practice gap.
Track completion¶
- Explain the core concepts, models, and methods of Computer Architecture
- Produce reproducible exercises, experiments, or designs with explicit checks