36-week on-ramp
Optional beginner lane. Week 1 of Tensor-to-Tenant assumes working programming comfort. If you do not have that base, take these nine resources in order on a 36-week budget. Skip the whole lane if you do not need it.
Not a gate. The 108-week curriculum is self-contained. Official page: https://sethuiyer.github.io/tensor-to-tenant/prerequisites/.
36-week budget
| Weeks | Phase | Resources | After this block |
|---|---|---|---|
| W1–2 | Learning how to learn | Google Like a Pro, How To Read Documentation, Git for Beginners | Search and docs fluency plus version control - the self-serve skills every later week compounds. |
| W3–6 | Computer science foundations | CS50x Lectures 1–6 | C, memory, and algorithms - the vocabulary of computation the course assumes at Week 1. |
| W7–10 | A computer from first principles | Nand to Tetris | From NAND gates to a CPU, compiler, and OS - nothing is magic anymore. |
| W11–16 | Mathematics for computer science | MIT 6.042J | Proofs, induction, counting, probability, and graphs - the exact reasoning Weeks 7–30 rely on. |
| W17–18 | Programming paradigms | YACR | Procedural, functional, OO, and let-it-crash - the lenses behind every framework you will read. |
| W19–28 | Statistical learning | Statistical Learning with Python | Supervised and unsupervised learning - the empirical core of the ML and evaluation weeks. |
| W29–32 | Software engineering at scale | Software Engineering at Google | Design docs, testing, code review, and ownership - the discipline that makes weekly artifacts professional. |
| W33–36 | Synthesis project | All of the above | Consolidate everything into one working project - then Week 1 of the arc starts on solid ground. |
Nine resources, in order
| Weeks | Resource | Focus | Outcome |
|---|---|---|---|
| W1–2 | Google Like a Pro - Advanced Search Operators | Finding the right source, fast | Self-serve research: filter, scope, and verify results instead of hoping Google guesses right. |
| W1–2 | How To Read Documentation For Beginners | Reading docs as a skill | Navigate any framework docs - quickstarts, references, and changelogs - without a tutorial. |
| W1–2 | Git for Beginners | Version control fluency | Commit, branch, merge, and recover - the tooling habit every weekly artifact depends on. |
| W1–6 | CS50x 2024 Lectures | Computer science fundamentals | C, memory, algorithms, data structures, and web - the shared vocabulary of the whole course. |
| W7–10 | Nand to Tetris | A computer from first principles | Build a working computer from NAND gates up - assembler, VM, compiler, OS - and a Tetris game. |
| W11–16 | MIT 6.042J - Mathematics for Computer Science | Discrete mathematics | Proofs, induction, counting, probability, and graphs - the reasoning the course front-loads in Weeks 7–30. |
| W17–18 | YACR - Programming Paradigms Explained | Programming paradigms | Procedural, functional, object-oriented, and let-it-crash thinking - and why each exists. |
| W19–28 | Statistical Learning with Python | Statistics and ML foundations | Supervised and unsupervised learning from the data side - the empirical backbone of every ML week. |
| W29–32 | Software Engineering at Google | Engineering culture and practice | How teams design, test, review, and ship at scale - the professional layer under the technical arc. |
Week pages
R01 · R02 · R03 · R04 · R05 · R06 · R07 · R08 · R09 · R10 · R11 · R12 · R13 · R14 · R15 · R16 · R17 · R18 · R19 · R20 · R21 · R22 · R23 · R24 · R25 · R26 · R27 · R28 · R29 · R30 · R31 · R32 · R33 · R34 · R35 · R36
Then start T2T Week 1.
Back to the syllabus.