Skip to content
Getting Digital

Machine Learning

Also: ML, statistical learning

Machine learning is the branch of computing in which a program works out its rule from examples instead of being handed that rule by a programmer, and is judged on how well the rule holds on cases it was never shown.

Assessment. Machine learning and statistics share almost all of their mathematics and part company over what they oblige you to defend: a statistical model must defend a claim about the world, a learned model need only defend its score on data it was forbidden to see during training. Settle which of those your problem requires before anybody opens a notebook, because the two produce different work and different arguments.

Machine learning is what you reach for when a rule exists but nobody can write it down. Ordinary software carries out instructions somebody typed; a learned system is shown inputs alongside the answers you wanted and derives the mapping itself. Nobody can specify line by line what makes a photograph contain a bicycle, or which invoices will go unpaid, yet both leave traces across enough cases for a model to pick up. The whole craft compresses into one word, generalisation: being right about situations that were absent from training. A model that reproduces its training set flawlessly and stumbles on anything fresh has failed, and it has failed in the most flattering way available, which is exactly why this discipline is built around withholding data and testing against it.

Readers ask constantly what divides this from statistics, and it is not, disappointingly, the mathematics. Regression, likelihood, optimisation and the trade-off between bias and variance belong to both. What differs is the question and the referee. A statistician fits a model to say something defensible about a population: which effect is real, how large, how certain, under which assumptions, with coefficients a human being has to interpret. A practitioner here fits a model to minimise error on data kept back from training, and will happily accept something nobody can interpret provided it wins on that data. Hence one side worries about violated assumptions while the other worries about the test set leaking into training. Neither party is the serious one. They answer to different judges, and plenty of confused hiring follows from pretending otherwise.

Three ways a model gets its lessons

Supervised learning is the workhorse: every example arrives with the right answer attached, a spam flag or an eventual sale price, and the model learns the route from one to the other. Unsupervised learning gets no answers and hunts for structure instead, grouping customers whose behaviour rhymes or isolating the transaction that resembles nothing around it. Reinforcement learning has no fixed answers either, only a score it earns by acting, which suits games, routing and control. In practice the borders blur and most production work is supervised, simply because most organisations already keep records of what happened next. Neural networks and deep learning cut across all three; they are a family of models within the field rather than an alternative to it. Every style rests on data analysis done beforehand, because a model inherits whatever is wrong with the table behind it, and inherits it without comment.

In practice

A subscription business wants to do something about cancellations, and one table of account history supports two entirely different projects. Fit a logistic regression, read its coefficients, and you hold a claim the product team can argue with: accounts that hit a failed payment in the preceding month go on to cancel at a markedly higher rate, together with the uncertainty around that. Fit a boosted ensemble on the identical columns and you hold something else: a ranked list of who will leave next month, scored on months the model never saw, carrying no story anyone can put on a slide. The first supports a decision about billing policy. The second supports a phone call on Tuesday morning. Picking the wrong project is how teams finish with either an accurate ranking nobody acts on or a tidy explanation that never becomes an action.

Often confused with

Deep Learning
A family of models living inside this field rather than a rival to it. Every rule about generalisation and held-out testing applies to those models unchanged.
Data Analysis
Analysis interrogates the data you already hold and reports what it found. A learned model is scored on data withheld from it, which is a stricter and narrower obligation.
Large Language Models
A very large product of this discipline, and an unrepresentative one. Most models earning their keep are small, tabular and dull, and the dull ones still run more of the economy.

Key takeaways

  • →The rule is derived from examples, never written in advance, and the only verdict that counts comes from cases held back during training.
  • →The mathematics overlaps with statistics almost completely; the goal does not, and the goal decides which tool your problem deserves.
  • →Coverage matters more than volume. A model cannot learn from an event that never appeared in front of it, however many rows sit around that gap.

Related concepts

  • More specificDeep Learning

    Deep learning is a sub-field of machine learning.

  • NLP is an application area of machine learning.

  • Learn firstPython

    Modern machine learning is written mostly in Python.

  • Machine learning and data analysis share foundations and skills.

  • More specificMLOps

    MLOps is the operational sub-discipline of machine learning.

  • Fairness and accountability questions arise wherever learned models make decisions about people.

Courses that teach this

Where this concept sits in the field

Certifications that test this

Vendor exams whose syllabus covers this concept: facts, cost and a preparation path on each page.

FAQ

Is this just statistics with better marketing?
It is statistics with a different obligation and a different culture. The markers are practical: held-out testing as the arbiter, tolerance for models nobody can interpret, and a willingness to ship a prediction that resists explanation. Anyone insisting the gap is nil has never had to defend an assumption to a regulator; anyone insisting the two are unrelated has never fitted a regression.
How much data does a project need?
Less than people expect when the task is narrow and the examples represent the real traffic, and more than anyone budgets when the cases you care about are rare. The binding constraint is usually coverage rather than volume: the awkward situations have to be in there, because nothing can be learned from an event the model has never met.

Sources

The primary text this definition rests on. Read it before relying on this one.

Last reviewed 26 September 2026 · Getting Digital