The Psychology of Doom

September 30, 2026 · c4573.org

🔊 Listen to this post
A magnifying glass enlarges one warning while a broad city of useful tools stands beneath a sunrise.

1. The New Tool Will Ruin Everything

The end of the world has an excellent business model. The deadline can fail, the explanation can change, and the customer can remain frightened enough to renew. Most businesses have to deliver something. This one can invoice you for a future that never arrived. Technology gives the business a fresh catalog: writing, printing, the internet, artificial intelligence. New machinery, same announcement. Humanity has finally gone too far. Please subscribe for updates.

Start with Socrates, with one correction to the usual internet version. In Plato's Phaedrus, Socrates recounts a story in which King Thamus criticizes writing: people will rely on external marks instead of exercising memory and mistake possessing information for understanding it. This is a philosophical dialogue, not evidence that Socrates organized an anti-book pressure group. The objection is subtler than the meme, and part of it remains useful.

You can copy an explanation without understanding it. A written page cannot answer your follow-up question. Those are limitations worth examining. The leap from a limitation to the ruin of the human mind is where the wheels come off. External memory also lets knowledge survive the person who learned it. Socrates' criticism reaches us because Plato wrote it down. The prosecution's case is being delivered by the defendant.

Writing changes what we practice remembering. It also lets someone learn from a mind that stopped breathing centuries ago. We can inspect an argument, correct it, and hand the correction forward. The tradeoff is real; the catastrophe does not follow. A tool can weaken one habit while expanding the work a person can do. The honest comparison counts both. Otherwise the diagnosis of intellectual decay becomes a complaint that nobody needs your preferred exercise anymore.

In 1492, Abbot Johannes Trithemius defended handwritten books in In Praise of Scribes. His concerns included the durability of parchment and the spiritual discipline of copying. Then his defense appeared in print in 1494. The University of Cologne's library describes the irony: printing helped circulate the argument for handwriting. This wasn't a cartoon villain trying to ban every press. He valued a practice and feared what would disappear with it.

That distinction matters because institutions often confuse their method with their purpose. Preserving knowledge is a purpose. Having a monk reproduce every sentence by hand is a method. If a better method arrives, the purpose may flourish while the institution loses its position. To the person inside that institution, these can feel like the same event. Civilization is in danger, announces the department whose services civilization has just learned to obtain elsewhere.

Fast-forward to 1995. Clifford Stoll's Newsweek essay about the internet doubted visions of online commerce and newspapers being replaced by networks. His skepticism about substituting computer access for an education had substance. His dismissal of major practical uses aged rather differently. The internet acquired problems, abuses, and powerful landlords. It also acquired the uses he doubted. A forecast can recognize a genuine weakness and still miss the trajectory completely.

Every new aid raises a fair question: what skill should people still learn for themselves? A calculator doesn't make arithmetic education pointless. A search engine doesn't make source criticism optional. An AI answer doesn't become true because it arrives quickly. But insisting that everyone perform every intermediate step unaided can turn education into a tollbooth. We should teach the judgment required to use a tool, including when to put it down, rather than define competence as refusing help.

Now the old complaint has a new vocabulary. Artificial intelligence will make people lazy, erase understanding, and end meaningful work. Some particular uses can damage learning. Someone who delegates every difficult step may learn less. Someone who uses a system to explain, test, and challenge their reasoning may learn more. Specify the activity and measure the result. A verdict about every human mind is a little ambitious for someone who has inspected three screenshots.

The common failure is treating today's limitation as tomorrow's ceiling, or treating a changed practice as the destruction of the goal. That failure can belong to enthusiasts too. A polished demonstration doesn't establish reliability. In The Helicopter and the Hike, we argued for tools that extend human work while preserving judgment. The promise is useful capability. We still owe each other proof that a particular tool delivers it.

There is a practical test hiding underneath the cultural argument. Does the tool help somebody finish a real task, and can that person recognize when it fails? Compare time, error, cost, and dependence. An assistant that saves an expert effort may confuse a beginner. A system useful for drafting may be unacceptable for an irreversible decision. These distinctions give us something to improve. Announcing that tools destroy thinking gives us an applause line and no specification. Engineering begins where the sweeping verdict ends.

2. Please Consult the Revised Apocalypse

Technology panic has a more theatrical relative: the world ends on a date. The date lends precision to an argument that hasn't earned it. A calendar looks wonderfully authoritative beside a frightening diagram. Before we reach the modern editions, consider two older ones. The people who believed them were people, with families and fears. Their dignity survives the prediction's failure. The prediction's claim to knowledge does not.

1524: the flood panic. An almanac by Johannes Stöffler and Jakob Pflaum forecast major changes around planetary conjunctions in February 1524. Other astrologers turned the celestial arrangements into warnings of a great deluge. Research accompanying a surviving almanac traces the escalation and the failed flood prediction. A calculation of where planets would appear became a claim about what water would do. Accurate arithmetic cannot rescue an invented causal bridge. The stars were arranged; the reasoning wasn't.

1844: the Great Disappointment. The Millerite movement settled on October 22 for Christ's return after earlier expectations had failed. The National Museum of American Religion recounts the disappointment when that return did not occur. You don't need to mock faith to reject somebody's claim that they have solved God's appointment calendar. The human cost belongs to the followers. The burden of explanation belongs to the people who claimed certainty.

Now five major modern cases. They are different kinds of failure, and putting them in one drawer would conceal the most useful lesson. A fabricated disaster, an overconfident forecast, and a real danger successfully mitigated are different things. If we can't tell them apart, our anti-doom argument is just another sloppy product with a reassuring label.

1968: The Population Bomb. Paul Ehrlich's book forecast hundreds of millions of starvation deaths in the 1970s despite emergency efforts. In their 2009 retrospective, Paul and Anne Ehrlich acknowledged underestimating the Green Revolution's expansion of food production. Regional famines and environmental damage were real; the forecast's fatalism still outran what happened. People improved the system the prediction treated as inadequate. The future had the impudence to include people working on it. Apparently they hadn't read the conclusion.

2000: Y2K. Software that stored years with two digits could mishandle the rollover from 1999 to 2000. This was a real engineering problem. Governments and businesses inspected, repaired, and tested systems. The U.S. Government Accountability Office attributed limited rollover disruptions to leadership and partnerships. Saying nothing happened, therefore the warnings were nonsense, is like thanking your smoke alarm for being a fraud because the fire department arrived. Prevention changes outcomes. That's the entire fucking point of prevention.

The mockable part of Y2K is the leap from vulnerable software to inevitable civilizational collapse. The admirable part is the work. This example cuts against the doomer and the smug spectator alike: the catastrophe wasn't inevitable, and success didn't mean there had been no problem. If an AI warning produces a tested defense and prevents harm, give it credit. If it produces only a bestseller, ask what actually became safer.

2008: the Large Hadron Collider. Fears that particle collisions would create a black hole and swallow Earth became an apocalypse story. Safety assessments reviewed the proposed mechanisms, including evidence from natural high-energy cosmic-ray collisions and astronomical observations. The argument was examined, rather than answered with a demand that everyone trust a lab coat. Earth wasn't eaten. Asking for a safety case was reasonable. Treating a dramatic possibility as an established outcome wasn't.

2011: Harold Camping. The broadcaster announced a May 21 rapture and an October 21 end of the world. Both dates passed. Later, Camping acknowledged the predictions were wrong. Good. Changing your mind is the adult response to failed evidence. We can laugh at apocalypse arithmetic without requiring someone to remain wrong for our entertainment. The followers had already paid enough. The forecast doesn't earn immunity, but an admission deserves more respect than another recalculation.

2012: the Maya calendar. December 21 became a world-ending deadline attached to the end of a Long Count cycle. NASA explained that a calendar cycle ending did not imply the world ending; the accompanying astronomical disaster stories lacked a sound basis. The Maya weren't responsible for every modern fantasy marketed in their name. Your wall calendar runs out in December too. You buy another one. You don't board up the windows because the stationery industry has exhausted spacetime.

Somebody can have believed a bad forecast without belonging to a defective category of human. Most of us have trusted a confident person and later regretted it. A claim needs to survive examination; a reader doesn't need to survive a humiliation ritual to join the examination. We can leave an argument we inherited without losing our place among other people. Nobody should have to defend a missed apocalypse to preserve their self-respect.

The recurring problem is unearned certainty. Sometimes a forecast ignores adaptation. Sometimes it invents a mechanism. Sometimes it sells inevitability where engineering offers choices. These failures give us reasons to demand a better argument from the next prophet. They don't prove that no catastrophe can happen. History doesn't issue safety certificates. It does provide a rather crowded complaints department for people selling the last chapter.

3. Why Doom Feels Smart, and Who Can Afford It

Why does the same routine keep working? Because a frightening story meets normal human machinery, then gets amplified by institutions that reward attention. You don't have to be stupid. You need something worth protecting, uncertainty about how to protect it, and a confident person who explains that your anxiety is evidence. That combination can catch a researcher, a mechanic, a developer, or somebody reading this paragraph and nodding a little too vigorously.

Loss aversion gives the threatened present an advantage. In prospect theory, Kahneman and Tversky describe decisions relative to reference points, with gains and losses carrying different weights. You can picture the competence, salary, or role you might lose. The potential gain has no memories attached yet. The loss has a face. The gain has a slide deck. And nobody pays this month's rent with a chart of aggregate welfare.

A worker's loss can also be real. Calling someone biased because their employer captured the productivity gain would be obscene. We made that argument in Ghost GDP: more output doesn't automatically compensate the displaced person. An average is a wonderful place to hide a victim. The response must give people access, bargaining power, and a share of useful capability. Advertising abundance while concentrating ownership is an eviction notice with better graphics.

Status quo bias gives familiarity its own vote. Samuelson and Zeckhauser found that framing an option as the existing arrangement changes how often people choose it. In public arguments, old harms become scenery while new harms become indictments. A person making an error is Tuesday. A machine making one is a referendum on machines. Compare both on the same task, with the same error standard, and include what the old system already costs.

Negativity and availability work together. An international experiment on responses to news found stronger average physiological reactions to negative content, with substantial individual variation. The availability heuristic describes judgments influenced by how easily examples come to mind. One spectacular failure circulates a thousand times. Ordinary successes disappear into work. Your feed supplies vivid memories, then your brain mistakes the selection for a sample. A headline isn't a denominator.

Declinism adds an edited past. Research on the illusion of moral decline found a persistent belief that people were becoming less moral without the matching decline in repeated assessments of contemporaries. This doesn't prove every condition is improving. It exposes one way memory and exposure distort comparison. Yesterday has family photographs. Today has a global incident feed. Also, childhood felt simpler partly because somebody else was handling the electricity bill.

Then the incentives arrive. Pessimism sounds serious because it names complications. Naming them is useful; converting them into inevitability is a separate claim. Attention can pay for the warning before reality grades it. Keep a record: outcome, probability, time window, mechanism, and evidence that would change the estimate. A failed deadline, a low-probability non-event, and successful prevention need different evaluations. Otherwise every result becomes another reason to renew the subscription.

Now consider the luxury of demanding that progress wait. Picture a comfortable, college-educated city resident whose food, shelter, and services reliably arrive. Other people harvest, haul, clean, repair, and lift. Their bodies absorb costs that scarcely appear in the resident's account of civilization. From that position, slowing everything can feel like prudence. From a twelve-hour shift, preserving everything can look like a request to keep carrying somebody else's comfort.

This isn't a census of AI critics. Pew's 2025 surveys found the U.S. public substantially more concerned about AI than the surveyed experts. Worry isn't an elite monopoly, and manual workers have every right to fear exploitation. The class question is whose costs a proposed response counts. If you have security, time, and professional influence, your ability to wait doesn't establish that everyone else can afford your timetable.

A small repair shop might use cheaper intelligence to work through manuals, compare parts, translate instructions, or prepare estimates. A worker might learn a skill without paying an expensive intermediary. These are possibilities to test, not promises that software can instantly roof a house. A useful assistant could reduce some drudgery surrounding physical work. Dismissing that because it doesn't resemble your preferred intellectual life mistakes a particular career's prestige for the definition of human benefit.

But if the employer owns the tools and pockets the gains, the worker may get a faster production target instead of an easier life. We owe that possibility the same scrutiny. The question running through this site's archive is ownership: can people keep, inspect, repair, and leave with the capability? Cheap cognition behind a permanent payment gate can make a landlord richer while leaving everyone else's dependency intact. Progress needs a distribution mechanism, not applause.

The classist move is treating existing deprivation as an acceptable holding pattern while people with insulation settle their philosophical concerns. Put the cost of delay beside the risk of deployment. Count the hours of avoidable work, the expensive help people can't obtain, and the barriers that keep useful knowledge from becoming practical independence. Then ask who bears each risk. A proposal for safety has to protect people who aren't already safe, including from the present.

Waiting is easier when you already have alternatives. If a service becomes expensive, you can hire help. If an institution fails you, you may know whom to call. The person without those options experiences the current system differently. A blanket demand to keep capability scarce protects the familiar arrangement for people it already serves. It leaves the excluded person waiting outside a door while the people inside hold a very sophisticated conversation about doors.

Make the proposed restriction specific. Which demonstrated hazard does it address? What activity remains available to independent builders? Who can appeal an error, and who can afford compliance? A costly permission system can protect an incumbent even when its author sincerely wants protection for the public. The burden is to show that the remedy improves safety without casually reserving useful capability for organizations rich enough to obtain permission. Good intentions don't make the bill disappear.

And apply that demand to the abundance salesman. Who receives the cheaper service? Who gains free time? Can the independent shop compete, or does a platform acquire another dependency? A forecast about total wealth isn't an answer. A practical route to more ownership is. Tools, accessible knowledge, and enforceable exits give people choices that a speech about the future cannot. Judge the result by the life it makes possible, including the person who cleans up after the conference.

If you recognize yourself in that comfortable position, there's a useful role available. Use your education and spare time to build defenses people can keep. Help test a system, explain its limits, document a repair, or make a tool maintainable outside your institution. You don't have to surrender your concern. Give it a job. Concern that produces an independently usable defense helps more than concern that appoints another permanent supervisor over everyone else's options.

The strongest objection remains: AI could create genuinely new dangers. The UK AI Security Institute's 2025 assessment found rising capabilities in software, cyber evaluations, and scientific assistance, alongside vulnerabilities in tested safeguards. It also cautioned against treating evaluations as forecasts of real-world impact. Capabilities, permissions, and deployment conditions matter. Failed ancient prophecies don't settle any of that. An uncertain catastrophic risk deserves investigation; uncertainty alone doesn't select the institution entitled to control the response.

Our answer is the build order in d/acc Has a Build Order: identify the harm, strengthen the defense, and inspect who owns the result. Constrain an agent's permissions. Preserve sources so claims can be checked. Make consequential actions reviewable. Publish reproducible tests and maintainable tools. Open capability can help attackers too; a release deserves scrutiny for what it enables and what cannot be undone. Concentrated capability deserves scrutiny for who can audit, contest, or escape its operator.

The destination is less scarcity and less suffering, with more people able to act for themselves. That requires judgment and engineering, including honest failures. It doesn't require a rational tribe laughing at the frightened tribe. The prophet can print another date. The corporation can print another promise. Neither gives you a tool you can keep. Build the defense. Publish the plans. Let people share the gains. The sun coming up buys another day to do the work.


c4573.org builds tools for people who want to own their stack. Read d/acc Has a Build Order for a practical approach to building defenses, or browse our tools.