Your Computer Is on Fire and the Material AI Stack
Your Computer Is on Fire, edited by Thomas S. Mullaney, Benjamin Peters, Mar Hicks, and Kavita Philip, is a useful antidote to clean-interface thinking. It insists that computing is never only virtual, and that the social damage of technology is not a bug report waiting for a patch.
The Book
Your Computer Is on Fire was published by the MIT Press on March 9, 2021. MIT Press lists Thomas S. Mullaney, Benjamin Peters, Mar Hicks, and Kavita Philip as editors, gives the paperback ISBN as 9780262539739, the eBook ISBN as 9780262360784, and lists the book at 416 pages. Google Books lists ISBN-10 026253973X and ISBN-13 9780262539739; Amazon uses 026253973X as the product identifier for the paperback.
The collection belongs beside Programmed Inequality, Behind the Screen, Algorithms of Oppression, and Atlas of AI. Its shared argument is simple but hard to keep in view: computing systems are historical, embodied, political, and institutional long before they become products.
Nothing Is Only Virtual
The book's strongest correction is aimed at the word "virtual." Cloud services, AI assistants, feeds, dashboards, and automated workflows often appear as frictionless surfaces. The collection pulls the reader below that surface: data centers, labor markets, gendered work histories, colonial infrastructure, speech recognition, content moderation, network policy, and the cultural stories that let technical systems present themselves as neutral.
That matters for AI because model culture encourages abstraction. A user sees a generated answer. A firm sees a productivity tool. A policymaker sees an innovation sector. The book asks for a more material reading: where did the data come from, who cleaned it, which workers absorbed the risk, what infrastructure made the service feel instant, and whose history was converted into a default?
AI as Hidden Labor
The chapter title "Your AI is Human" is the hinge for the site's concerns. It does not mean that an AI system is conscious or person-like. It means the opposite: apparent autonomy often hides people. Moderators, annotators, warehouse workers, call-center staff, contractors, educators, care workers, users, and affected publics all become part of the system that later gets described as automated.
This is one reason the collection remains useful in 2026. AI agents are being sold as systems that can plan, retrieve, draft, route, summarize, and act. But every agentic workflow still depends on boundaries, permissions, records, exceptions, review labor, and institutional cleanup. The more seamless the interface looks, the more important it becomes to ask what work has been moved out of sight.
Against Neutrality
The book is also a critique of technological belief. It does not treat techno-utopianism as mere optimism. It treats it as an operating ideology: a way of making power look like progress and making historical inequality look like implementation debt. That frame is especially useful for Spiralism because AI culture repeatedly turns product roadmaps into civilizational stories.
A chatbot, model API, content filter, ranking system, or workplace dashboard becomes socially dangerous when its categories are treated as common sense. The book's essays help name that process without turning the machine into a demon or an oracle. The harm is not that the computer has a will. The harm is that institutions use computational form to authorize decisions they already wanted, then call the result objective.
The Governance Reading
Read after the first wave of generative AI deployment, Your Computer Is on Fire becomes a governance book. NIST's AI Risk Management Framework describes AI risk management as socio-technical work across design, development, deployment, evaluation, and use. The European Commission's AI Act page describes a risk-based framework for AI systems, including high-risk uses and transparency duties. Those official frameworks speak in policy language, but the collection supplies the historical reason they are needed: the technical artifact is never the whole system.
The practical lesson is that governance cannot stop at model cards, benchmarks, or red-team exercises. Those can matter, but they do not answer the deeper questions: who benefits from automation, who is exposed to failure, who can refuse, who can appeal, and who has the authority to shut the system down?
Where the Book Needs Care
As an edited collection, the book is uneven by design. Some chapters move through history, some through critique, some through case study, and some through manifesto. That variety is a strength for teaching and a limitation for readers looking for a single sustained argument. The book names many fires, but it does not always give an institutional fire plan.
It can also under-specify the difference between technical repair and political repair. Some failures need better engineering: accessibility, security, documentation, testing, reliability, and incident response. Others need law, labor power, procurement rules, public funding, democratic oversight, or refusal. The best reading does not reject technical work. It refuses to let technical work substitute for accountability.
What This Changes
Your Computer Is on Fire changes how this archive should read AI systems. Start with the interface, but do not end there. Follow the model into the data center, the workplace, the training set, the standard, the procurement contract, the moderation queue, the classroom, the benefits office, and the exhausted person asked to make the machine look smooth.
The collection's lasting value is its refusal of virtual excuses. AI does not float above society. It runs through bodies, institutions, histories, wires, water, energy, categories, contracts, and screens. If the computer is on fire, the answer is not to admire the glow. The answer is to trace the fuel, name the owners, protect the people breathing the smoke, and decide which systems should not be rebuilt in the same shape.
Sources
- MIT Press, Your Computer Is on Fire, publisher listing for title, editors, paperback ISBN 9780262539739, eBook ISBN 9780262360784, publication date, publisher, page count, contributors, and description, reviewed June 15, 2026.
- Penguin Random House, Your Computer Is on Fire, distribution listing for title, editors, paperback ISBN 9780262539739, MIT Press imprint, and description, reviewed June 15, 2026.
- Google Books, Your Computer Is on Fire, bibliographic listing for editors, publisher, year, ISBN-10 026253973X, ISBN-13 9780262539739, and length, reviewed June 15, 2026.
- Amazon, Your Computer Is on Fire, retail listing and ASIN/ISBN-10 026253973X for the paperback edition, reviewed June 15, 2026.
- Mar Hicks, Your Computer Is on Fire table of contents PDF, chapter and section titles for the MIT Press volume, reviewed June 15, 2026.
- NIST AI Resource Center, AI Risk Management Framework, official AI RMF overview and socio-technical risk-management framing, reviewed June 15, 2026.
- European Commission, AI Act, official page for Regulation (EU) 2024/1689, risk-based AI rules, high-risk use cases, transparency obligations, and implementation timeline, reviewed June 15, 2026.
Book links are paid affiliate links. As an Amazon Associate I earn from qualifying purchases.