You On AI Field Guide · Andrej Karpathy The You On AI Field Guide Home
TxtLowMedHigh
PERSON

Andrej Karpathy

The engineer who named the new era of software—builder of Tesla’s Autopilot vision system and OpenAI founding member who saw, from inside the machinery, that programs were no longer written but grown, and gave the world its clearest vocabulary for what that means.
Andrej Karpathy arrived at artificial intelligence not as a philosopher asking what minds are but as an engineer asking what software is—and from that vantage he saw something the philosophers missed. Working inside Tesla’s Autopilot team, he watched handwritten C++ shrink and neural networks swell, absorbing functionality engineers had always specified by hand. He named what he was witnessing: Software 2.0, a change not of degree but of kind, in which the dataset becomes the source code and gradient descent writes the logic no human will ever read. When large language models made plain English a programming language, he extended the account to Software 3.0, and in a line that would pass into the working vocabulary of a generation he wrote that the hottest new programming language is English. His sharpest gift, though, is not coinage but calibration: he holds at once that the transformation is structural and that artificial general intelligence remains years away, that these systems are genuinely remarkable and that their intelligence is jagged—brilliant on some peaks, startlingly weak in the adjacent valleys—and that we are not building digital animals but summoning ghosts, statistical echoes of human text rather than evolved minds with drives of their own.
Andrej Karpathy
Andrej Karpathy

In the [YOU] on AI Field Guide

The cycle that began with [YOU] on AI is fundamentally a story about a change in the substrate of computation, and Karpathy is the person who named that change most precisely. Where Edo Segal describes the consumer-facing surface—a hundred dollars a month buying what once required a team of engineers—Karpathy describes the engine. The democratization Segal celebrates is downstream of the fact that the act of programming has changed so completely that anyone who can describe what they want can now attempt to build it. Claude Code and its siblings are Software 3.0 in operation; the orange pill moment is what Software 3.0 feels like from the user’s side.

His framework also supplies the cycle’s most rigorous account of why the transformation is partial. Karpathy insists the systems are jagged: expert in some domains, elementary in others, with no smooth surface connecting the peaks. The same model that drafts a competent legal brief will confidently miscount the letters in a word. This jaggedness is not a transitional bug but a structural feature of optimizing for narrow objectives—the systems were shaped by imitating human text, not by living in the world, which is why Karpathy calls them ghosts rather than animals. The cycle’s portrait of the human difference—consciousness, the wondering self that asks why—finds its engineering complement in Karpathy’s ghost framing: the difference is not a matter of degree along a single scale but a difference of origin, written into how each kind of thing came to exist.

His concept of the autonomy slider offers the cycle’s most practical answer to how humans and machines should work together during the decade of transition. Rather than a binary between full human control and full machine autonomy, he proposes a continuum calibrated to the cost of verification in each domain. Where checking the machine’s output is cheap, autonomy can be high; where a confident error causes real harm, the human must stay close. The Trivandrum training session Segal describes—twenty engineers redirected from execution to judgment—is the autonomy slider moved thoughtfully upward, with the human migrating from writing every line to supervising, verifying, and steering.

Ascending Friction
Ascending Friction

What places Karpathy in the cycle’s gallery of indispensable thinkers is the combination of deep technical authority and intellectual honesty about the limits of his own field. He could have let vibe coding stand as an uncomplicated celebration of AI-assisted development; instead he spent considerable effort explaining its scope conditions, insisting on the distinction between play and production. He could have extrapolated the steep early stretch of the capability curve into an imminent arrival of machines that match us across the board; instead he says the timeline is longer than the hype suggests, that reinforcement learning as currently practiced amounts to sucking supervision through a straw, and that the most important work ahead is not making the model bigger but building the surrounding system—the memory, the tools, the orchestration—that turns raw capability into reliable application.

Origin

Born in Bratislava and raised in Toronto, Karpathy studied computer science at the University of Toronto before earning his doctorate at Stanford under Fei-Fei Li, where he created and taught CS231n, the university’s first deep learning course. In that classroom he developed the pedagogical instinct that would define his public career: the conviction that you do not truly understand a thing until you have built it yourself from first principles, that the demystification of difficult machinery is itself an act of empowerment. He went on to become a founding member of OpenAI and then director of artificial intelligence at Tesla, where his years leading the Autopilot vision system gave him an education that purely linguistic AI does not provide—the education of trying to make a machine act reliably in the physical world, where mistakes have weight and the environment does not cooperate.

At Tesla, Karpathy confronted the long tail: the endless parade of rare situations, each individually improbable but collectively constant, that the system has never seen and must nonetheless handle correctly. A driving model that is brilliant in ninety-nine percent of situations and catastrophically wrong in the remaining one percent is not ninety-nine percent of the way to a solution; it is dangerous. His response was the data engine—a disciplined loop of identifying failures in the field, collecting and labeling the relevant data, and retraining to close the gap—and from this experience he drew the lesson that the decisive variable in most real-world AI applications is not the architecture but the diet, the quality and composition of what the system is trained on. Software 2.0 was not a theory he developed in a seminar. It was a description of what was already happening to the codebase under his supervision.

After Tesla he returned to OpenAI briefly before founding Eureka Labs in 2024 with the conviction that the same technology he had spent his life building could transform how people learn—that an AI tutor, properly designed, could offer every student the kind of patient, personalized instruction that has historically been available only to the privileged few. In 2026 he joined Anthropic’s pretraining team. Across every role, his most durable contribution may be neither a model nor a company but a sequence of lectures: Neural Networks: Zero to Hero, in which he builds the core machinery of modern AI from nothing, in plain code, assuming only basic Python and a hazy memory of high-school calculus, and carrying the learner all the way to a working miniature of the transformer.

Key Ideas

Software 2.0. Karpathy’s central claim is that software is undergoing a change of kind rather than degree. Software 2.0 replaces explicit human-written instructions with learned weights: humans specify a goal and a rough architecture, and an optimization process discovers the actual program. The source code is the dataset; the compiler is training; the binary is the trained network. This inverts the entire activity of programming, shifting prized skill from algorithmic cleverness to data judgment—knowing what examples the model needs, recognizing gaps in its experience, and curating them into existence. The programmer’s relationship to the resulting artifact is unlike anything in the history of the craft: you built it, but you cannot read it.

The LLM as a new kind of computer. Karpathy resists metaphors that frame large language models as minds. The metaphor he reaches for instead is computational: the LLM is a new kind of computer, and we are in the early, primitive period of its operating system. The context window functions like working memory; the model’s weights function like a vast read-only store of knowledge. He has compared frontier model capability to an electrical utility—produced by a small number of capital-intensive providers and distributed to vast numbers of consumers who pay by the token—and to a semiconductor fabrication plant: a small set of immensely sophisticated, expensive facilities at the frontier of what is physically and economically possible.

Jagged intelligence. The capability profile of large language models is not uniform. It is jagged—brilliant in places, startlingly weak in others, with no smooth surface connecting the peaks and valleys. The jaggedness is not a bug being slowly fixed but a structural feature of optimizing for narrow objectives, and it means that competence in one region licenses no confidence in any adjacent region. The fluency of a language model is seductive; it speaks in the register of expertise even when it is wrong, and its mistakes do not announce themselves. Jaggedness is a discipline of humility about a system that invites overconfidence.

Ghosts, not animals. Large language models are not digital animals shaped by evolution under survival pressure. They are ghosts—statistical echoes of human text, fluent because they were trained to reproduce the patterns of human expression, but lacking the embodied, evolved substrate that grounds a real mind. They have no body, no survival pressure, no continuous existence, no stake in the world. The ghost framing dissolves a great deal of confused thinking: systems that lack animal drives will not turn on us like predators, but they will also lack the embodied common sense that any creature learns through a body acting in the world.

The autonomy slider and the decade of agents. Rather than a binary between full human control and full machine autonomy, Karpathy proposes an autonomy slider—a continuum the human adjusts depending on the task, the stakes, and the trustworthiness of the system. The constraint on agent capability is not primarily the intelligence of the underlying model but the difficulty of verifying that the agent did the right thing. Where verification is cheap, autonomy can be high; where a confident error causes real harm, the human must stay close. Karpathy calls the coming period the decade of agents, choosing a decade deliberately as a rebuke to those announcing the age has already arrived.

The Chess Complementarity Shift
The Chess Complementarity Shift

Debates & Critiques

The central debate around Karpathy’s framework concerns whether the ghost will eventually become the animal—whether imitation, scaled far enough and combined with reinforcement from consequences, will produce something that crosses whatever line separates sophisticated pattern-matching from genuine cognition. Karpathy holds the question open: he has watched these systems do things that the simple story of mere imitation does not easily explain, generalize to genuinely novel problems, combine ideas in ways absent from any single training example. He does not claim the line can never be crossed; he claims it has not been crossed yet and that crossing it is harder and further off than the enthusiasts believe. A sharper dispute concerns his 2015 dismissal of AI existential risk as analogous to worrying about overpopulation on Mars. Critics argue the capabilities that have since emerged have moved the analogy from apt to dangerous—that a system shaping millions of cognitive environments daily is closer to a consequential threat than a Martian colony problem. Karpathy’s defenders respond that the present harms remain the tractable ones: the displaced worker, the biased deployment, the mismatch between impressive demo and reliable product—and that attention diverted to distant catastrophe systematically neglects the concrete problems engineering can actually address. A third debate concerns the data engine philosophy and its distributive implications: if the dataset is the source code, then the labor embedded in internet-scale human text is the labor embedded in the program—and the question of who owns that labor, and who benefits from it, becomes one of the central distributive questions of the age that Karpathy’s framework sharpens without resolving.

The Three Eras of Software

Karpathy’s account of how the substrate of computation changed
Era One
Software 1.0
Explicit code, written by humans in programming languages. The programmer is the author; every behavior the machine exhibits can be traced to a line someone wrote on purpose. The prized skill is algorithmic cleverness. The barrier to entry is formal syntax.
Era Two
<a class="wiki-link" href="../med/software_2_0.html">Software 2.0</a>
Learned weights, compiled from data by gradient descent. The source code is the dataset; the programmer’s job shifts from authorship to cultivation. The program is a black box not by design but because opacity is the price of letting the machine discover its own logic.
Era Three
Software 3.0
The prompt, written in plain English. The model is the computer; natural language is the programming language. The barrier to entry collapses from formal syntax to the ability to describe what you want—and billions of people already have that ability.

Further Reading

  1. Andrej Karpathy, “Software 2.0,” Medium (2017) — the essay that named the paradigm shift
  2. Andrej Karpathy, Neural Networks: Zero to Hero (YouTube lecture series, 2022–2023) — builds GPT from scratch in plain code
  3. Andrej Karpathy, “The Busy Person’s Intro to Large Language Models,” (YouTube, 2023)
  4. Andrej Karpathy, Dwarkesh Podcast conversation (2025) — on ghosts, timelines, and the decade of agents
  5. Andrej Karpathy, “Vibe Coding,” X post (February 2025) — the phrase and its scope conditions
Explore more
Browse the full You On AI Field Guide — over 8,500 entries
← Home0%
PERSONBook →