How machines learn
The word "learning" in machine learning invites a misleading picture. Nothing in the process resembles a student sitting with a textbook. What actually happens is closer to a very patient, very fast process of adjustment: the system makes a guess, measures how wrong it was, nudges itself slightly in a better direction, and repeats — millions of times.
That loop is the core idea. Everything else is engineering around it. This lesson walks through it without mathematics.
Learning as guided adjustment
Imagine you want a system that estimates an apartment's rent from its size, neighborhood, and age. You have records of several thousand apartments where both the features and the actual rent are known.
The system begins with a set of internal numbers — call them parameters — set to essentially arbitrary values. You feed it the first apartment's details. It produces an estimate, and that estimate is badly wrong, because the parameters are arbitrary.
Now the crucial step. You compare the estimate against the known rent and compute the size of the error. Then you adjust each parameter slightly in whichever direction would have reduced that error. The adjustment is small and deliberately so: you are not trying to fix this one example, you are trying to move gradually toward parameters that work across all examples.
Repeat this across every apartment in the data, then repeat the whole pass many times over. Errors shrink. The parameters settle into values that capture real relationships in the data — larger apartments cost more, certain neighborhoods carry a premium.
This process is called training, the error measure is called a loss function, and the direction-finding procedure is called gradient descent. The vocabulary is worth knowing, but the intuition is what matters: repeated small corrections guided by measured error.
Note
The system is never told the rule. It is only told how wrong it was. Every relationship it ends up representing was inferred from the examples, which is why the composition of the training data determines so much about the final behavior.
Three ways of learning
The loop above describes supervised learning, where each training example carries a correct answer supplied by a human or by a recorded outcome. Most commercially deployed machine learning is supervised: spam or not spam, fraudulent or legitimate, this image contains a tumor or it does not. The main constraint is that labeled data is expensive, because labeling usually requires human effort.
Unsupervised learning works on data with no answers attached. The system is asked to find structure — grouping customers with similar purchasing behavior, or flagging transactions unlike anything it has seen before. There is no ground truth to check against, so results require human interpretation to be meaningful.
Reinforcement learning replaces labeled answers with rewards. An agent acts in an environment, receives a score, and adjusts its strategy to increase the score over time. This is the approach behind systems that learned to play games at a very high level. It suits problems that are naturally sequential, and it needs an environment where the system can practice cheaply and repeatedly — which is why it is far less common in ordinary business settings than supervised learning.
Testing on what it has not seen
Here is the most important discipline in the whole field, and the one most often misunderstood by people evaluating AI products.
A model that performs beautifully on its training data may be worthless. It could have effectively memorized those specific examples rather than learning generalizable relationships. This failure is called overfitting, and it is the reason practitioners always hold back a portion of the data — a test set — that the model never sees during training. Performance on that held-out data is the only accuracy figure worth trusting.
The intuition is familiar. A student who memorizes the answers to last year's exam has learned nothing you would want to certify. The only meaningful assessment uses questions the student has not seen.
The practical version of this for you as a professional: when someone quotes an accuracy number, ask what it was measured on. If it was measured on the training data, it is not evidence. If it was measured on held-out data that resembles your actual use case, it is meaningful. If it was measured on held-out data drawn from a very different population than yours, treat it as a rough upper bound rather than a promise.
From simple models to neural networks
The rent example used a handful of parameters. Modern systems use the same loop with dramatically more of them, arranged in layered structures called neural networks. Each layer transforms its input and passes the result forward; stacking layers lets the system represent relationships far more intricate than any straight-line rule.
The learning procedure does not fundamentally change. Guess, measure the error, adjust everything slightly, repeat. What changes is scale — and scale is what made the current generation of systems possible.
The video below builds visual intuition for what a neural network is and how those layers relate to each other. It is worth the time.
What to carry forward
Three ideas from this lesson will keep returning throughout the course.
Learning is adjustment guided by measured error, not comprehension. The training data determines what the system can represent, including its blind spots. And a model's quality is only demonstrated on data it has never seen.
Knowledge check
A vendor reports that their model achieves 99 percent accuracy. What is the first thing you should ask?