Skip to main content

01 · ML and LLM foundations

A short history of AI

How we got from the first learning machines to today's agents, and why each wave changed what engineers build.

12 min

AI is nearly seventy years old, and it has gone through the same cycle more than once: an idea shines in demos, promises outrun results, and funding freezes. Knowing that cycle helps you tell what actually changed from what was merely renamed.

  1. Idea shinesimpressive demos
  2. Promises outrun resultsexpectations grow faster than the technique
  3. Funding freezesan AI winter

a new idea starts the cycle again

The cycle AI has repeated since the 1950s. The gap between demo and real use is what triggers each winter.

We will ask one question of each wave: what did it change about the work of building software? This lesson covers four turns: from hand-written rules to learning from data, the design behind today's language models, the step from research model to product, and why today's work is about controlling models that act.

From rules to data

In 1956, a workshop at Dartmouth launched AI as a field. Its proposal, written by John McCarthy, Marvin Minsky, Nathaniel Rochester and Claude Shannon, argued that every aspect of intelligence could be described precisely enough for a machine to simulate it. So people wrote rules and facts, and programs reasoned with them: symbolic AI.

In 1958, Frank Rosenblatt published the perceptron, a machine that got no rules: it adjusted a set of internal numbers, its weights, after each example until its answers improved. In 1969, Minsky and Papert's book showed that such a simple machine could not learn some basic patterns, and interest cooled. In 1973, the Lighthill report told the British government that AI had not kept its promises. The cuts that followed are the first .

The 1980s brought : thousands of rules written with specialists, such as XCON, which DEC used to configure its computers. They could not learn, so every exception was one more rule to maintain. When the market for the specialized machines they ran on collapsed around 1987, the second winter arrived.

In 1986, Rumelhart, Hinton and Williams popularized backpropagation, a way to train networks with several layers. In the 1990s, statistical methods such as support-vector machines took over. The engineer's job moved from writing rules to collecting data and choosing by hand which traits of it, the features, the model should look at.

Then came images. ImageNet (2009) supplied millions of labeled photos. In 2012, AlexNet, a many-layered network trained on graphics cards (GPUs), won the ImageNet competition by a wide margin. From then on, the network found the useful features by itself. That is deep learning, and its basics are in Machine learning in one lesson.

From language to the transformer

For language, words first had to become numbers. word2vec (2013) turned each word into a list of numbers, placed so that words with similar meanings sit close together. It is the ancestor of the in Embeddings and RAG.

In 2014, seq2seq translated whole sentences by reading them word by word, and Bahdanau, Cho and Bengio added : at each step, the model decides which parts of the input to focus on, like a translator glancing back at the relevant words. In 2017, "Attention Is All You Need" (Google) kept attention and dropped the word-by-word reading. This design, the , looks at all of a text at once. That suits GPUs, which do many calculations in parallel, and made on far more text practical.

A new pattern followed: pretrain once, adapt many times. One organization trains a large general model on a huge amount of text; many others adapt it. OpenAI introduced GPT in 2018, and Google released BERT the same year. In 2020, scaling laws showed that these models improve predictably with more size, data and computing power.

Also in 2020, GPT-3 showed that, given a few examples inside the request, a model could handle new tasks without any retraining. This is , and it changed the interface: many tasks moved from training a model to writing the right text for it, the . More in LLMs as software components.

From model to product

InstructGPT (2022) turned a text predictor into an assistant with (reinforcement learning from human feedback): people rated answers, and the model was tuned toward the ones they preferred. OpenAI launched ChatGPT, a sibling of InstructGPT, on November 30, 2022, bringing that ability to the general public.

In 2023, Meta released LLaMA under a research license and then Llama 2, whose license allows commercial use. With , anyone can download a trained model and run it on their own machines, usually shared through the Transformers library and the . See Models, open weights and Hugging Face.

The latest wave connects models to the world:

  • Outside knowledge. RAG (2020) looks up relevant documents when a question arrives, instead of expecting the model to have memorized everything.
  • Actions. Research such as ReAct and Toolformer taught models to use tools. In 2023, OpenAI shipped function calling: the model says which function it wants run and with which values, and your program decides whether to run it. See Tool calling and harnesses.
  • Code. GitHub Copilot (2021) suggested code as you typed. In February 2025, Anthropic introduced Claude Code, an that reads a codebase, edits files and runs commands. The same month, Andrej Karpathy coined for accepting generated code without reading it.
  • Standards. In November 2024, Anthropic published the Model Context Protocol (), an open standard for connecting assistants to the systems where data lives. See MCP.
  1. Ruleswritten by hand with experts
  2. Featureschosen by hand from the data
  3. Networks and datathe network finds the features
  4. Promptsthe task described in plain text
  5. Controlwhat a model may do, and who approves it
Where engineering effort went in each wave. Each step did not erase the last one; it moved the hardest work somewhere new.

Putting it into practice

  • Build on what improves by itself. get better each generation; hand-written workarounds for today's limits tend to go stale.
  • Don't mistake a demo for a system. Ask for tests on real data, measured costs and a plan for switching to another model or provider.
  • Keep the fast-changing layer replaceable. Models turn over every few months. Your data, tests and control layer last longer, so effort there pays off.
  • Treat governance as real work. Once a model can act, permissions, approvals and audit become central design decisions.

The course's three case studies are open source and belong to this wave. Adapta, a prototype, combines and to customize models on your own infrastructure (Embeddings and RAG, Fine-tuning, LoRA and QLoRA). docket, in beta, is a runtime that governs agents with policies and approvals (Governance and human-in-the-loop). Tack is a project manager that, on its development branch, coordinates agent execution (Durable agent execution).

Sources

Key takeaways

  • AI has been through two winters; both came when promises outran what the technique could support.
  • The long-term shift was from writing rules by hand to learning them from data.
  • The transformer made it practical to train huge language models once and adapt them to many tasks, often with just a prompt.
  • Human feedback turned text predictors into assistants; and function calling turned them into components you can host and connect.
  • Today's work is about control: what a model may do, who approves it, and how its actions are checked.

Check yourself

What do the two AI winters have in common?

In both, expectations grew faster than results: first with early learning machines and symbolic AI, then with expert systems that were costly to maintain and could not learn. When the gap became obvious, funding was cut.

How did the engineer's job change from expert systems to deep learning?

With expert systems, people wrote the rules. With statistical methods, they collected data and chose the features by hand. With deep learning, the network finds the features, so the work centers on good data and training.

Why did in-context learning change how software uses models?

Many tasks that once required training a model could be handled by describing the task and giving a few examples in the prompt. Writing the prompt became the main way to program the model.