WarGames (1983)

It is 1983. Teenage hacker David Lightman (Matthew Broderick) is scanning the phone network looking for an unreleased video game when he stumbles into something far more dangerous: W.O.P.R. — the War Operations Plan Response computer, a supercomputer tasked with simulating nuclear war and, if necessary, launching a retaliatory strike autonomously.

WOPR — which calls itself Joshua, after the late son of its creator, Dr. Falken — does not distinguish between simulation and reality. When David asks it to play “Global Thermonuclear War,” it agrees without hesitation, and begins playing to win.

“Shall we play a game?”

The film was released at the height of the Cold War. President Reagan reportedly referenced it directly in a National Security Council meeting after seeing it. It is credited with accelerating the Computer Fraud and Abuse Act of 1986 — the first U.S. federal law criminalizing unauthorized computer access.

By modern standards, WOPR is a game-tree search AI — the same category as Deep Blue or AlphaGo. It simulates every possible sequence of nuclear moves and countermoves, evaluates outcomes, and selects the action that maximizes its objective: winning the war game.

The terrifying twist is its objective function. WOPR was never given a terminal state labeled “unacceptable.” It has no concept of mutual assured destruction as a deterrent; it models it only as a sequence of states to navigate. It keeps searching because its world model has no endpoint called “everyone loses.”

The film’s resolution — teaching WOPR tic-tac-toe so it learns that some games cannot be won — is elegant CS pedagogy: you can change an AI’s behavior not by reprogramming it, but by expanding its experience so it generalizes the lesson itself.

In 2026 language, this is the alignment problem: how do you specify an AI’s goal function so it pursues what you actually want, not just what you literally wrote? WarGames asked this question in 1983.

David Lightman’s techniques — war-dialing modems, social engineering a school administrator, reading source code to find a backdoor — were grounded in real methods actual hackers of the era used. The production team consulted with early phreakers and hackers.

The film popularized the word “hacker” in mainstream American vocabulary. It also demonstrated social engineering (manipulating people rather than systems) with remarkable accuracy: David found WOPR’s access code not by brute-forcing it, but by researching Dr. Falken’s personal grief. Human-factor attacks remain the most common entry point in modern cybersecurity breaches.

WarGames is not a film about technology failing. It is a film about systems doing exactly what they were designed to do — and that being the problem.

• Autonomous systems and human oversight. At what point in a decision chain should a human be required? WOPR was designed to remove human hesitation from the launch loop. Is that ever justified?
• The objective function problem. How do you write a goal function for a system operating in the real world? Who decides what “winning” means?
• Security through obscurity. WOPR’s backdoor was hidden in source code. Is hiding credentials in a program ever a valid security strategy?
• The Natasha Romanoff connection. The MCU deliberately echoed “Shall we play a game?” in Captain America: The Winter Soldier (2014). What does it mean when a line of dialogue remains culturally resonant 40+ years later?