Question 1
Cory Doctorow
Author websiteNovelist and public-interest technology writer who argues for useful tools, worker power and limits on corporate control.
How will AI change the world?
Across: his expressed Doom–Bloom outlook. Up: scale of transformation.
Doom–Bloom: 34 out of 100. Scale of transformation: 61 out of 100. Interpretation ranges: 25 to 50 horizontally, 50 to 75 vertically. These are interpretation coordinates, not event probabilities.
≈12%
Inferred from his simulated answers, not a number they gave. Plausible range: 6–24%.
A central assumption
It only needs powerful institutions to deploy it at scale.Answer 2
If this assumption turned out differently, how would his outlook change?
An unresolved question
I don’t have a defensible percentage, and I won’t manufacture one.Answer 3
What would help him distinguish the plausible outcomes here?
What could change their mind
A repeatable demonstration that these systems can reliably handle genuinely surprising situations—not merely extend familiar patterns—would change my view substantially.Answer 4
What evidence would be enough, and in which direction would it move his view?
More details
Substantial benefits are expected, with important conditions or distribution limits.
57 / 100
Interpretation range 33 to 67 on the qualitative scale.
Severe or widespread harm is a material expected part of the future.
67 / 100
Interpretation range 67 to 67 on the qualitative scale.
Human choices can substantially redirect the AI trajectory.
74 / 100
Interpretation range 50 to 100 on the qualitative scale.
Restrict the AI uses discussed until prior protections or permission are in place.
Simulated position: Allow the AI uses discussed with targeted accountability and protections.
Minimize restrictions on the AI uses discussed.
These interpretations keep his stated conditions. Benefits and harms can both be substantial. The ranges describe how we read his simulated answers, not statistical confidence intervals.
Similar worldviews
Thought leaders whose simulated worldviews are closest to Cory Doctorow’s
What Cory Doctorow has said about AI
Doctorow distinguishes useful AI tools from the investment bubble and argues that workers should control how automation affects their work.
“Designing autonomous, malicious software is generally considered irresponsible and dangerous.”
Pluralistic, LLMs are real, AI is fake “I use a local chatbot to spellcheck these posts.”
Pluralistic, Discernment “AI is a normal technology.”
Pluralistic, Three more AI psychoses “AI can write code, but AI can’t do software engineering.”
Pluralistic, Code is a liability (not an asset)
Word for word from the linked sources, checked Oct 3, 2026
Simulated Assessment
Sources
Articles, interviews, and writings used to ground this simulated user.
Accepts statistical extrapolation as useful and finds the plausibility of generated language genuinely surprising. Argues that theory-free extrapolation has hard limits: statistical regularity is not understanding, and unexpected situations require a theory of what is happening. Criticizes diminishing returns, resource consumption and replacing workers with defective chatbots. The argument concerns these methods, not an experimentally established ceiling on every possible AI architecture. Main essay inspected.

Argues low switching costs and competing open-weight models undermine hyperscalers’ ability to recover investments. Even granting improved unit economics for argument’s sake does not solve continuous competition. Suspects superintelligence restrictions could excuse incumbent collusion and prohibit alternatives. Calls for investigating concrete misconduct rather than blessing restraints of trade. These are his economic and political claims, not audited company accounts or a comprehensive position on every possible pause. Main essay inspected.

Adopts a distinction between actual language-model hacking tools and stories that models woke up or set new goals. Interprets the Hugging Face incident as foreseeable behavior of an inadequately supervised hacking workflow. Still calls automated malicious software dangerous, especially against fragile infrastructure. Wants better sandboxes, supervision and a prohibition on government vulnerability hoarding. Executives’ quoted 10% extinction claim is not his estimate. Main essay inspected; incident forensics and linked podcast not independently audited.

Describes using a local, offline LLM to find typos, retaining his own editorial judgment. Cannot evaluate a sophisticated mathematics dialogue and refuses to mistake its impressive appearance for verified validity. Distinguishes expert checking from asking a chatbot to teach unfamiliar material. Suggests teachers could generate and validate fresh test questions rather than be replaced by bots. Considers retrieving his own essays with a local model, but describes that as an idea, not a deployed system. Main essay inspected.

Accepts personal utilities and disposable software as useful even when they are not maintainable production systems. Distinguishes worker-directed centaurs from workers forced to serve automation. Endorses the importance of making code legible and reusable for future teams, while warning investment imperatives reward replacement and cleanup is undervalued. Reports programmers’ divergent experiences without treating either as universal. Main essay inspected.

Calls AI normal technology and the bubble exceptional. Criticizes investors, bosses and critics who amplify exceptionalism. Accepts skilled practitioners’ modest enthusiasm for useful automation plugins, while retaining serious resource, labor and political concerns. Main essay inspected.

Argues noncopyrightability of machine output protects human creative labor, whereas a new training right could be assigned to concentrated employers and used to replace workers. Favors sectoral bargaining and cites writers’ negotiated ability to choose AI use without being forced. Allows brainstorming when generated words stay out of the final work. His legal interpretation is not independently validated here. Main essay inspected.

Distinguishes writing working code from engineering legible systems that fail gracefully amid changing context. Warns that maximizing code output produces maintenance liabilities and chained agents compound reliability problems. Accepts validated routine code and isolated, one-off utilities. His digital-asbestos analogy predicts lasting cleanup burdens, not a measured job forecast or guaranteed employment program. Main essay inspected.

Expects a damaging investment crash but productive residue: skilled people, inexpensive hardware and open models, with more optimization possible. Praises local transcription, image generation, data conversion and privacy-preserving voice assistance. Does not know how many giant foundation models would survive; zero is a possibility rather than a certainty. Main essay inspected.

Where do you land?
Map my worldview