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 Doing the Work — 9 sections, 79 lessons. Show all 14 areas
The judgement calls nobody teaches — what to build, what to compare against, and how to know your numbers are honest.
9 sections 79 of 79 lessons published
Deciding what to build, whether machine learning is even the right answer, and how you will know it worked.
11 published
Start with something dumb that works, then find out honestly whether anything fancier is actually better.
9 published
A loss curve is a message from your model about what is going wrong. This section teaches you to read it.
7 published
A score that looks amazing is usually a bug, not a breakthrough. Here is how to hunt down the leak before someone else finds it.
11 published
Getting the same number twice, and keeping track of hundreds of runs without losing your mind.
6 published
Turning a working notebook into code that another person — including you in six months — can actually run.
7 published
Turning a PDF full of equations into code that runs, and knowing which papers deserve your weekend.
9 published
Build real things. Every project has full code, a dataset and a deployment guide.
9 published
What AI and ML interviews actually ask in each round, with worked answers — not career platitudes.
10 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.