Most people who decide to learn artificial intelligence spend their first three weeks doing the wrong thing. They buy a course, watch nine videos, hit a gradient descent derivation full of partial derivatives, and quietly stop opening the tab. Six months later the progress bar reads 4%.
That is rarely a discipline problem. It is a sequencing problem. AI is a stack of skills that has to be assembled in a workable order, and a lot of beginner material teaches them in an order that breaks people. What follows is the order that tends to hold up, with realistic hour counts and the things you can safely skip.
Get the maths to functional, then stop
You do not need a maths degree. You need enough to read a formula and know what it is doing. That is a much smaller target than most syllabuses suggest, and 15 to 25 hours of focused work usually gets you there.
Linear algebra: about six hours
Vectors, matrices, matrix multiplication, dot products, transposes. The goal is to look at Wx + b and see a transformation of a data point rather than a wall of symbols. 3Blue1Brown’s Essence of Linear Algebra series runs around three hours and covers more intuition than a semester of lectures you’ll half-remember.
Probability and statistics: about eight hours
Distributions, expectation, variance, conditional probability, and Bayes’ theorem. This is the part people underestimate. A model that outputs 0.83 is making a probability claim, and you need to be able to argue with it.
Calculus: the chain rule, and that’s basically it
Backpropagation is the chain rule applied repeatedly. Learn what a derivative means geometrically, learn how the chain rule composes functions, and move on. Skip multivariable calculus for now. You can pick it up later if you ever need to derive something from scratch.
Write code that touches real data before you touch a model
A surprising number of people try to learn neural networks while still shaky on pandas. That produces the worst kind of frustration, because you can’t tell whether the bug is in your model or in your dataframe.
Spend two weeks on Python fundamentals plus numpy and pandas. Load a CSV, filter rows, group by a column, plot a histogram. Then open scikit-learn and work through the same three lines over and over: fit, predict, score. Start with the Titanic dataset (891 rows, 12 columns) and a random forest. You should land somewhere around 78-80% accuracy. Then repeat the whole exercise on California housing with a regression model.
If you learn better with structure, a guided walkthrough of how an online AI class takes you from signup to a shipped project is worth reading before you commit to a platform, because the good ones front-load exactly this kind of hands-on work.
Build three projects, in this order
Projects are where the learning actually consolidates. Three is enough to be credible, and the order matters because each one introduces a new failure mode.
- Tabular prediction (10-15 hours). Pick a dataset you genuinely care about: rental prices in your city, local football results, your own electricity bills. Clean it yourself. Ship a notebook that loads raw data and ends with a prediction.
- Text classification (10-15 hours). Grab 5,000 reviews or support tickets. Use TF-IDF plus logistic regression first. Only reach for a transformer if the simple version plateaus, and be honest about whether it does.
- Image model (10-15 hours). Take 200 photos of your own, fine-tune a pretrained model, and see what happens. This is the project that teaches you about data quality faster than any lecture.
Accuracy is not the point. Finishing is. A repo with three complete, messy, working projects beats a folder of half-finished tutorials every time, and it’s what an interviewer will actually look at. If you want a sense of how much ground a structured course covers in the same window, this breakdown of what an AI class covers hour by hour is a useful reality check.
Choose a learning structure that fits your actual week
The right format depends less on prestige than on how many hours you can reliably protect. Be honest about that number, because a 20-hour-a-week plan built on a 5-hour week collapses in week two.
If you have four hours a week
Go self-paced and free. Alison’s free AI courses cover the vocabulary and basic concepts without a subscription, and they pair well with a slow project build. Expect the three projects above to take four months rather than ten weeks.
If you have twelve hours a week and a deadline
A cohort-based or university-branded programme earns its cost here, mostly through structure and peer pressure. Executive formats like the Oxford artificial intelligence programme suit people who need the credential alongside the content, though they assume a working schedule. Before paying for anything, run the shortlist through a six-step method for choosing AI programmes so you’re comparing outcomes rather than marketing pages.
Read one paper a month, badly at first
Papers are not gatekept, they’re just badly formatted for newcomers. Start with Attention Is All You Need (2017, fifteen pages). Read the abstract, then the figures, then the conclusion. Skip the proofs entirely on the first pass. You’ll understand maybe 40% and that’s fine, because the second paper will be easier and the fifth will feel routine.
Keep a one-paragraph note on each: what problem, what approach, what result. Twelve of those notes in a year is a genuine education in how the field moves.
The traps that quietly cost people months
Tutorial hell is the big one. If you’ve completed four courses and have zero repositories, the courses are not helping. Stop buying and start building.
Chasing the newest model is the second. Learning last year’s architecture properly teaches you more than skimming release notes for this year’s. Related: GPU envy. You do not need a graphics card to learn artificial intelligence. Google Colab’s free tier will train everything in the plan above.
Learning in silence is the third. No output, no feedback, no correction means you can hold a wrong mental model for a year without noticing. Post your work somewhere, even if three people see it.
Set a ship date, not a syllabus
Pick a date ten weeks out and name the thing you will have finished by then. “A working rent predictor plus a written post explaining what didn’t work” is a real goal. “Learn AI” is not, because you can never tell whether you’ve hit it.
Then work backwards. Weeks one and two on Python and pandas. Weeks three and four on maths, in parallel with a first scikit-learn model. Weeks five through nine on the three projects, roughly two weeks each. Week ten to write it up, publish it, and pick the next target.
Keep a public commit streak going. Sixty small commits over ten weeks will teach you more than any single course, because every one of them represents a problem you hit, debugged, and got past. That log is also the most honest evidence you’ll ever have that you actually learned the thing.