Saltar a contenido

tutoriaal-companion learning material for AI_EXPERT_ROADMAP.md

This folder is the how of the roadmap. The roadmap (../AI_EXPERT_ROADMAP.md) tells you what to build each week and why. This folder tells you how to learn what you need-with sources, sequencing, math, code skeletons, and an explanation of how each piece earns its place in the journey.

2026 hardening update: a new DEEP_DIVES/ directory contains 14 self-contained reference chapters (~131,000 words). These chapters let the reader master each topic from the document alone-without depending on the YouTube videos, blog posts, or paper PDFs that the sequences link to (and which will rot over years). The sequences and weeks remain the how to learn cadence; the deep dives are the primary technical reference. See DEEP_DIVES/README.md for the index, and AUDIT.md for the durability analysis behind the addition.

Restructured for 3 deep-dive sessions per week

The folder was originally organized as a Mon–Fri daily checklist. It is now organized as 3 deep-dive sessions per week, because deep blocks beat fragmented daily ticks for absorbing technical material. The new shape:

Session Theme Time When (suggested)
A Theory & Foundations 2.5–3.5 h weekday evening
B Implementation & Build 3–4 h weekend morning
C Synthesis, Eval, Ship 2–3 h weekend afternoon

Total per week: ~9–11 hours of focused work. If your real availability is closer to 6 hours, run the year over 18 months instead of 12-same plan, halved velocity. Pretending otherwise is the most common failure mode.

Why three sessions, not five days

Five short daily blocks fragment context. You re-load every morning and ship nothing in any single sitting. Three long sessions let you re-derive a proof from foundations to its application in attention, all in one block. Material sticks because it's connected. Code shipped because there was uninterrupted time to debug. The week's narrative arc-read → build → ship-happens in one weekend, not over a week of partial attention.

Inside each session: foundations → intermediate → advanced

Each session is internally structured as a mini-curriculum: - Part 1-Foundations (~30–60 min): the simplest version of the idea, with worked examples. - Part 2-Build-up (~45–90 min): the intermediate concepts that connect foundations to application. - Part 3-Advanced (the level the journey requires) (~45–90 min): the form in which you'll actually use the idea later-in attention, in evaluation, in fine-tuning.

This mirrors how the best textbooks teach: spiral from a concrete simple case to the general advanced formulation, with the connection always visible.

Two kinds of documents

1. `sequences/ - topic deep-dives

Each file takes one topic (linear algebra, transformers, RAG, evals, etc.) and walks from basics to the required advanced level, explaining at each rung why this rung matters for the AI-engineer journey. Use these when: - You need to learn a topic without skipping prerequisites - You're stuck on something and want to know what's underneath it - You're preparing for a quarter (read the relevant sequence in advance)

2. `DEEP_DIVES/ - self-contained reference chapters (14 files)

Each chapter is the durable primary source for one topic-math derivations, algorithm proofs, design patterns, runnable code, and worked exercises. Authored to be readable across years even as external links rot. See DEEP_DIVES/README.md for the curriculum-pairing index.

Topics: - 01_MATH_FOR_ML.md - applied LA/calc/probability with full derivations. -02_PYTORCH_FLUENCY.md - user-side PyTorch (complement to AI_SYSTEMS internals). - 03_CLASSICAL_ML_RIGOR.md - the foundations skipped at your peril. -04_DEEP_LEARNING_FUNDAMENTALS.md - backprop derived; AdamW; norms; init. - 05_LLM_APPLICATION_PATTERNS.md - daily-work engineering (structured outputs, tool use, caching, retry, orchestration). -06_RETRIEVAL_AND_RAG.md - BM25 to RRF to RAGAS, fully derived. - 07_AGENT_RELIABILITY_ENGINEERING.md - distributed-systems lens applied (the bridge chapter). -08_EVALUATION_SYSTEMS.md - the user's specialty: golden sets, judges, kappa, power, A/B. - 09_LLM_OBSERVABILITY.md - the user's unique moat: OTel GenAI conventions, SLOs, dashboards. -10_FINE_TUNING_SFT_TO_RLHF.md - LoRA, QLoRA, DPO derived end-to-end. - 11_MULTIMODAL_FOUNDATIONS.md - ViT, CLIP, LLaVA, Whisper, diffusion (gap-fill). -12_AI_SAFETY_AND_RED_TEAMING.md - production defense engineering (gap-fill). - 13_AI_FOR_SRE_BRIDGE.md - the unique-moat lift that the curriculum had underweighted. -14_FUTURE_PROOFING_AND_AUDIT.md - the durability framework + refresh cadence.

3. `weeks/ - week-by-week training plans (3 sessions each)

One file per week of the 12-month plan (48 files: weeks/M01-W01.md through weeks/M12-W04.md). Each file contains: - The week's goal and artifact - Prerequisites (what you must know coming in) - Three sessions with: arc, parts, math derivations or code skeletons, resources with links, self-check questions, common pitfalls, output committed at end of session - End-of-week artifact and self-assessment - Common failure modes for the week

How to use a weekly file

  1. Pre-week (Sunday, 30 min): read the file end-to-end. Queue up the videos / paper / chapter for Session A. Confirm you have the prerequisites.
  2. Session A (~3 h): do the theory block in a single sitting. Take notes. Do all self-checks before stopping.
  3. Session B (~3–4 h): open Session A's notes for reference. Build. Don't context-switch out.
  4. Session C (~2–3 h): finish artifact, run evals if applicable, push code, write blog post if due.
  5. End of week: mark the file's checkboxes. Carry slipped items into next week's Session A as a "warmup recap."

Index

Deep Dives (the primary technical reference)

Curriculum hardening artifacts

Sequences

Weeks

  • Q1-Foundations: weeks/M01-W01.md … weeks/M03-W04.md
  • Q2-Applied AI Engineering: weeks/M04-W01.md … weeks/M06-W04.md
  • Q3-Specialization + Infra: weeks/M07-W01.md … weeks/M09-W04.md
  • Q4-Synthesis + Public Portfolio: weeks/M10-W01.md … weeks/M12-W04.md

Conventions

  • Math: rendered inline using ‖a‖, θ, etc. (plain Unicode, readable in any markdown viewer). Where derivations span multiple lines, code blocks are used.
  • Code: Python skeletons are runnable; copy and extend, don't paste-and-pray.
  • Links: durable sources (arXiv IDs, official docs, well-known author blogs). When a URL is uncertain, the doc names the resource so you can search for it.
  • Self-check questions: answerable from the session content. If you can't answer, redo the part.
  • Output of session: always a concrete artifact-notebook cell, repo commit, hand derivation photographed, blog draft. No session ends with "I read about X."
  • Free-first. Where a paid course is recommended, a free alternative is also listed.
  • Three sessions, not five. Block them in your calendar Sunday evening.

On the cadence and life

If you miss a session, don't panic-double-up. Skip it and continue. Three sessions/week sustained over 48 weeks beats four sessions/week for 12 weeks followed by burnout. The goal is compounding. Compounding requires consistency more than intensity.

If life forces a 4-week pause (vacation, illness, family), restart with the next session, not the missed one. The plan accommodates ~4 lost weeks/year by design.

Print this path

Want to read offline or archive? Open the printable version - every section of this path concatenated into one page, styled for paper. Use your browser's Print → Save as PDF.