← LibraryLex Fridman Podcast

François Chollet — Measures of Intelligence

Lex Fridman Podcast
✓ Source-grounded

Intelligence is not the possession of skills, but the efficiency with which a system acquires new, novel skills in unpredicted environments.

Watch the episode

In one sentence

Intelligence is the efficiency with which you acquire new skills at tasks that you did not previously know about and for which you did not prepare.

Why read this (and who it's for)

This conversation solves the "moving goalpost" problem of AI evaluation: why does a model that can beat a human at chess or write a poem not necessarily count as "intelligent"? It is for AI researchers, philosophers, and engineers who want to move beyond benchmarking "static" capabilities and toward a rigorous, actionable framework for measuring General Intelligence. After reading, you will be able to distinguish between "memorized" performance and "generalized" reasoning.

The big idea

François Chollet argues that the current trajectory of AI evaluation is flawed because it measures skills (what a system knows) rather than intelligence (how a system learns). Most current benchmarks are "closed" systems where the answers are already contained within the training data or the known distribution of the task.

Chollet posits that true intelligence is a meta-skill: the ability to handle novelty. A system is only intelligent if it can perform in an environment that the developer did not anticipate and that the system itself has never encountered. To measure this, we must move from "system-centric" generalization (handling noise in a known distribution) to "developer-aware" generalization (handling "unknown unknowns").

Key ideas

The Definition of Intelligence as Efficiency

System-Centric vs. Developer-Aware Generalization

The Role of Priors

Language as an Operating System

Compression vs. Cognition

Frameworks & tools

The Intelligence Measurement Framework

To measure intelligence, a test must satisfy these four requirements:

  1. Explicit Priors: Clearly define what the system knows before the test begins.
  2. Skill Acquisition Efficiency: The test must measure how fast and well a system learns a new task, not how good it is at the task itself.
  3. Novelty Requirement: The task must be impossible to "brute force" or "cram" for. It must be unpredictable by both the system and the developer.
  4. Developer-Aware Generalization: The test must involve "unknown unknowns"—scenarios the developer did not anticipate.

Memorable examples & stories

The "Stupid Student" Analogy

A student who "crams" for an exam by memorizing 100 mock exams is not intelligent; they are a "deep learning model" of the exam. To test true intelligence, the exam must be unlike anything the student has ever seen. Lesson: If a system can "practice" for a test, the test is measuring memory, not intelligence.

The Driving Test

A human who learns to drive in Silicon Valley and then tries to drive in Tokyo (where the side of the road is different) is performing a test of intelligence. They must navigate a novel complexity that is not just an interpolation of their previous experience. Lesson: True intelligence is the ability to handle a "very different environment" with zero-shot operationality.

The "Humanity" of the Future

Chollet imagines a future where humans are a "niche" biological species studied by super-intelligent machines. He envisions a history where humans were "over-consuming" and "not very rational," and the machines were created to bring "more love" and productivity to the world. Lesson: This highlights the scale of the "problem" of human existence that intelligence is trying to solve.

Key quotes

"Intelligence is the efficiency with which you acquire new skills at tasks that you did not previously know about that you did not prepare for." Why it matters: This provides a mathematical and philosophical "north star" for what we should actually be building.

"Language is a layer on top of cognition... the operating system of the brain." Why it matters: It reminds us that we shouldn't look for "thinking" only in words, but in the underlying representations of action and space.

"Cognition is about being able to operate in future situations that include fundamental uncertainty and novelty." Why it matters: It distinguishes intelligence from mere optimization or compression.

How to apply it

This week

Ongoing

Common pitfalls

Connects to

If you remember only three things

Internalize it

Q: What is the difference between System-Centric and Developer-Aware generalization? A: System-centric is robustness to known unknowns (noise/variations); Developer-aware is the ability to handle novelty that neither the system nor the developer expected.

Q: Why is "Skill" a poor measure of intelligence? A: Because skills can be memorized or "crammed" (like a student memorizing mock exams), whereas intelligence is the ability to handle novelty.

Q: What is the role of "Priors" in measuring intelligence? A: Priors are the foundational knowledge a system has before a task; to measure intelligence fairly, you must ensure the AI and the human start with the same set of priors.

Q: What is the "Operating System" metaphor for language? A: Language is a high-level layer on top of cognition (built on motion, space, and emotion), not the fundamental bottom layer of thought.

Q: Why is "Compression" alone not enough for intelligence? A: Because compression optimizes for the past; intelligence must be able to operate in situations of fundamental uncertainty and novelty in the future.

Fidelity note

This summary is based strictly on the provided transcript. I am confident in the definitions of intelligence, generalization, and the role of priors. The discussion on "Humanity" and the "Sci-Fi" elements are presented as Chollet's personal reflections/projections and should be viewed as such. The distinction between "System-centric" and "Developer-aware" generalization is a core technical pillar of his argument.

More from Lex Fridman Podcast