Learning paths
An ordered route through the lessons for one job: ML developer, AI engineer, computer vision engineer.
Translation is unavailable right now. Your browser’s own “Translate page” usually works.
The whole curriculum, grouped into 14 areas. Start at the top if you are new. If you came here for one thing, filter to its area or search — everything is on this page or one click from it.
14 areas 117 sections 1,162 of 1,167 lessons published 10 new lessons every day
Showing Production and MLOps — 16 sections, 157 lessons. Show all 14 areas
Getting a model off your laptop and keeping it alive: data pipelines, serving, scaling, monitoring, cost and on-device.
16 sections 157 of 157 lessons published
Getting models out of your laptop and into the real world, reliably.
7 published
The unglamorous work that decides whether a model succeeds — getting good data and keeping it good.
13 published
Keeping the numbers a live model reads fresh, correct and fast — the part that breaks most often.
10 published
The server that sits between your trained model and a real user — how it loads, answers and stays up.
10 published
How to serve many users at once on the same hardware, instead of one at a time.
6 published
Measuring how fast your service really is, and working out how many machines you need before the traffic arrives.
10 published
The cheapest inference is the one you never run. How to reuse answers and keep the bill small.
13 published
The most expensive machine in your stack — how to size it, share it, and stop wasting it.
10 published
Adding and removing machines as traffic moves, and sending each request to the right one.
10 published
Knowing exactly which model is running, where it came from, and how to build it again next year.
6 published
Automatic checks that catch a broken model before your users do.
10 published
Putting a new model in front of users a little at a time, and taking it back quickly when it is wrong.
10 published
Your service is up and answering. This is how you find out whether the answers are still any good.
11 published
Seeing inside a chain of prompts, retrievals and tool calls when a user says the answer was wrong.
9 published
What to do at 2am when the model is wrong, slow or quietly broken — and how to be ready for it.
9 published
Running models on phones, browsers and tiny boards, where there is no GPU and no cloud.
13 published
An ordered route through the lessons for one job: ML developer, AI engineer, computer vision engineer.
Build real things with full code, a dataset and a deployment guide.
Every term you keep seeing, defined in one plain sentence first.
Paste the error you got. Find out what it means and how to fix it.