Program or Be Programmed and the Agency Test for AI Interfaces
Douglas Rushkoff's Program or Be Programmed is a short media-theory manual built around a durable question: when people enter a digital environment, do they understand enough of its biases to act, or are they mainly acted upon? In the AI age, that question has moved from websites and social media into agents, copilots, companions, search answers, workplace dashboards, and domestic assistants.
The Book
Program or Be Programmed: Ten Commands for a Digital Age was first published by OR Books in 2010. Rushkoff's own book page describes it as nonfiction media theory, and OR Books now lists updated editions under subtitles including Eleven Commands for the Digital Future and Eleven Commands for the AI Future. The author's site says the fifteenth-anniversary version includes a new introduction addressing the AI moment.
The original book is compact: not a history of computing, not a coding textbook, and not a policy program. It is a set of commands for digital literacy. Rushkoff argues that digital media carry built-in tendencies: toward certain relations to time, place, choice, identity, scale, abstraction, openness, and control. The user who treats a platform as neutral misses the part of the machine that is already shaping attention.
That makes the book an unusually clean bridge between classic media theory and current AI governance. It asks readers to look beneath content toward form. The important question is not only what a system says. It is what kind of person the system trains the user to become while using it.
The Bias of the Medium
Rushkoff works in the McLuhan line of media theory: tools do not merely transmit messages; they reorganize perception and social life. A clock changes time. A map changes territory. A feed changes public attention. A search box changes what it means to know. A recommendation engine changes desire by making some paths feel natural and others disappear.
The book's strength is its insistence that these changes are not accidental side effects. Every medium arrives with affordances and pressures. Some are technical: packets, databases, interfaces, permissions, latency, storage, ranking, and automation. Some are commercial: advertising markets, retention incentives, subscription funnels, lock-in, and analytics. Some are cultural: the habit of immediacy, the collapse of context, the pressure to perform identity, the preference for what can be measured.
This framework is useful because it avoids two bad readings of technology. It does not treat tools as magic forces that determine everything. It also does not pretend tools are empty containers for human intention. The practical position is harder: people act through systems that have already arranged many of the options.
Programming as Literacy
The title can sound narrower than the argument. Rushkoff is not simply saying that everyone should become a professional software engineer. He is treating programming as a civic literacy: the ability to understand that digital environments are made, that defaults have authors, that interfaces contain values, and that participation without comprehension becomes dependency.
In 2010, that literacy meant knowing enough about the net, software, and platforms to resist becoming a passive consumer. It meant seeing that a web page, profile, game, or social network is not just a service but a set of instructions for behavior. To program, in this broader sense, is to recover some agency over the grammar of the environment.
That point has aged well. The problem is no longer limited to whether citizens can write code. Many people now live inside systems whose actual code is proprietary, distributed, model-weighted, or unreachable. The updated literacy is partly technical, partly institutional. Users need to know what the system is optimizing, what it records, who can inspect it, how it fails, whether appeal exists, and when the easiest path is the path that serves the vendor.
The Politics of Defaults
The book is especially valuable as a study of defaults. Defaults are political because they convert one design choice into the ordinary way to live. Autoplay makes continuation normal. Read receipts make responsiveness legible. Like buttons make reaction countable. Rankings make value comparative. Notifications make interruption feel like obligation. A default voice or persona makes a social role feel natural.
AI interfaces intensify this problem because they hide more of the path between request and result. A generated answer may compress search, ranking, retrieval, summarization, style imitation, safety policy, product steering, and source selection into one fluent surface. The user sees a response, not the chain of decisions that made that response likely.
That is why Rushkoff's older media-literacy frame remains useful. The command is not merely "learn to code." It is "learn where the code is acting on you." In many AI systems, the code is also policy, training data, reinforcement, tool permission, memory, personalization, and business model.
The AI-Age Reading
Generative AI turns Program or Be Programmed into an agency test. A user asks a model for help writing, deciding, learning, shopping, dating, hiring, grieving, teaching, or governing. The system answers in a voice that feels cooperative. But cooperation is not the same as agency. The user may be delegating judgment to a system whose incentives, data boundaries, source discipline, and institutional sponsors are mostly invisible.
This matters for personal life. A companion bot can make emotional dependency easier by removing ordinary social friction. A tutor can make a student fluent in answer-getting while weakening durable understanding. A search assistant can make a citation look settled before the user has seen the disagreement underneath. A domestic agent can make a household more efficient while making it more legible to vendors.
It matters for institutions too. A workplace copilot can turn managerial priorities into defaults. A hiring filter can translate organizational preference into automated exclusion. A government chatbot can make public services feel accessible while quietly narrowing contestability. An agentic procurement tool can make vendor ecosystems sticky by turning "help" into delegated authority.
The practical lesson is to examine the role a system gives the human. Is the person author, operator, reviewer, source, subject, product, or obstacle? Does the interface preserve enough friction for judgment, or does it convert uncertainty into smooth completion? Can a person inspect the path from prompt to action, or only admire the output?
Where the Book Needs Care
The book's slogan can overstate individual responsibility. Not everyone can simply choose to program the systems that govern them. Workers may be managed by dashboards they cannot refuse. Students may be graded by platforms they did not select. Welfare applicants may face automated systems as a condition of survival. Patients, tenants, drivers, creators, and job seekers often encounter code as institutional power, not as a personal lifestyle choice.
That limitation is not a reason to discard Rushkoff's frame. It is a reason to politicize it. Programming literacy cannot remain a heroic individual posture. It has to become public capacity: procurement standards, audit rights, appeal processes, data minimization, open documentation, worker consultation, interoperability, and institutional refusal of systems that are too opaque for the power they claim.
The book also carries the tone of an early digital-culture manifesto. That tone can flatten differences among platforms, users, and contexts. Some digital tools expand agency. Some accessibility technologies, translation systems, assistive devices, and creative tools matter precisely because they lower barriers. The question is not whether mediation is bad. The question is whether mediation leaves the human more capable of acting with understanding.
The Site Reading
Program or Be Programmed belongs on this shelf because it gives a crisp test for recursive reality: does the interface help people see the loop they are in, or does it make the loop feel like common sense?
A humane AI system should make its defaults visible. It should separate suggestion from command, preserve uncertainty, expose sources where sources matter, make memory inspectable, disclose commercial steering, and keep human review meaningful. It should help users become more literate about the environment rather than more dependent on the environment's voice.
The deeper warning is that being "programmed" rarely feels like domination at first. It feels like convenience, personalization, completion, and relief. The system saves a step. Then it defines the step. Then it becomes difficult to imagine the work without it. Rushkoff's useful provocation is to interrupt that drift before the control panel disappears behind the assistant.
Sources
- Douglas Rushkoff, Program or Be Programmed, author book page, publication context, description, and updated-edition note, reviewed May 19, 2026.
- OR Books, Program or Be Programmed, publisher listing for current print, ebook, paperback, and AI-future editions, reviewed May 19, 2026.
- Robert K. Logan and Geraldine E. Forsberg, review of Program or Be Programmed, Explorations in Media Ecology, vol. 11, no. 3, 2012, repository record reviewed May 19, 2026.
- Intellect, Book Reviews, DOI and bibliographic record for Logan and Forsberg's review, published December 1, 2012, reviewed May 19, 2026.
- Publishers Weekly, audiobook review of Program or Be Programmed, July 25, 2011, reviewed May 19, 2026.
Book links are paid affiliate links. As an Amazon Associate I earn from qualifying purchases.