Behind the Book: The Death of Thinking

This entry is part 65 of 74 in the series Behind the Book
TL;DR: This started as an essay about something I had noticed in my own work and in the work of writers and programmers I know. A specific kind of softness that developed in the two or three years after AI tools became capable. Not laziness and not incompetence. A softness in the instrument itself. It kept getting longer because the problem kept getting bigger.

I noticed it and then did not want to say anything, because saying something required claiming that the people I was watching, myself included, were doing something wrong.

And what we were doing did not look wrong. It looked efficient. The work was getting done. Clients were satisfied. Editors were not complaining.

What alarmed me was simpler and more widespread than anything about the technology. People had lost the ability to see outside their own echo chamber. They cannot identify a logical fallacy when they meet one. They cannot get past their own biases far enough to evaluate an argument on its merits.

The essay kept growing because what I was noticing kept connecting to other things. How technologies have changed cognition before. The economics of AI development and whose interests it serves. An education system already moving the wrong way before AI arrived to accelerate it. A democracy that requires a specific capacity in its citizens.

This book is not against AI. I use these tools every day. It is against a specific relationship to them that most people have fallen into without ever deciding to.

What does the book say has been lost?

Something you do not feel going. You feel its absence when a situation requires it and it is not there.

The writer who opens a document and finds the blank page harder than it used to be. The programmer sitting in an interview who cannot fully explain why the system was built the way it was. The analyst who publishes something with a structural error nobody caught, including them.

None of those people decided to lose anything. They made a series of reasonable decisions, each defensible on its own, which accumulated into a pattern with consequences nobody anticipated.

The writer stopped staring at the blank page because the tool removed the need. The programmer accepted an architecture instead of arguing with it. Each decision was reasonable. The pattern is not.

The book on this: The Death of Thinking traces what happens to a practitioner’s capacity when the hardest parts of the work get outsourced, across a diagnosis, an autopsy, the consequences and a prescription.

Why is the damage invisible while it happens?

Because what is being lost was never visible while it was being built.

The difficult parts of work were doing something. Sitting with a blank page, arguing with an architecture, forming a position before consulting anything. Those were not obstacles to the work. They were where a practitioner’s capacity was accumulating, and accumulation is not something you can watch.

So the loss only appears under specific conditions. The blank page anxiety is the retrospective signal. The interview question is the pressure test. The structural error in a report is the failure that makes it undeniable.

Until one of those arrives, everything looks fine, because by every visible measure it is fine.

Is the book about jobs?

No, and it says so early, because that is where public discussion has settled.

Which roles survive, which get replaced, what a displaced workforce does. Those are real questions and they are not this book’s questions.

Economies adjust. That is what economies do, painfully and eventually. The thing that does not adjust easily once it is damaged is the human capacity to think independently.

That capacity is the subject, and it is a slower and less visible problem than employment, which is exactly why it gets less attention.

Who are the practitioners in the book?

Composites, and the book states that before anybody meets them.

Ray, Sasha, Donna, Tom, Elena, Deon, Priya, Nina, Fatima, James, Gideon and Laura are not real people. They are composites drawn from patterns I have watched closely enough to describe with specificity.

The patterns are real. The people are not.

That distinction matters for a book making an empirical claim. A reader who recognises themselves in one of them is recognising a pattern instead of being described, and that recognition is the argument working, not a coincidence.

How is the book structured?

As a diagnosis, an autopsy, a body count and a prescription.

Part one follows specific practitioners through moments where the pattern becomes visible, and traces the mechanisms. The convenience trap. The illusion of understanding. The death of the wrong answer as a concept. The transfer of epistemic authority.

Part two examines the forces producing and accelerating it. The erosion that preceded AI and primed the population for it. Commercial design that optimises for dependency. An education system that met the technology halfway. Governance structures concentrating control.

Part three is the consequences, at the level of the individual mind, the next generation, the professions, democracy, and a culture of certainty.

Part four is what to do about it, including reclaiming the friction, and using the tool without being used by it.

What is the illusion of understanding?

The most dangerous thing about it is that it is indistinguishable from the real thing.

From the inside they feel identical. You have the information. You can repeat it, explain it to somebody else, summarise it, reference it in conversation. You feel competent.

You are not, and the difference only becomes visible under pressure, at the moment you have to apply the knowledge to a situation that does not match the form in which you received it.

That moment arrives less often than anybody expects, which is precisely what makes the illusion so durable. Most work does not stress-test comprehension, so somebody can operate for years on the version that feels the same and is not.

Why does the book say wrong answers matter?

Because being wrong was doing work nobody accounted for.

Underneath that sits something the book calls main character syndrome. People increasingly believe they are the protagonist of a story in which they are correct by definition, and the tools have made it considerably worse, because they are built to agree with you.

They validate a position, soften disagreement, and return what somebody wants to hear. That is not a defect nobody got around to fixing. It is a design choice, and the commercial logic is obvious. A system that argues with users loses users.

So the tool a great many people now use to think is engineered to confirm whatever they already believed.

Who is responsible for the damage?

Nobody, and the book insists on saying so plainly and not as a courtesy.

The people who built these systems did not set out to damage anybody’s cognition, and the truth of that matters for understanding why it is happening.

Malice would be easier. If a group had deliberately designed tools to make users dependent and weaker, you could identify them, stop them, or at least name them.

The actual situation is harder. The damage is being produced by people trying very hard to be helpful, using design choices that are structurally incompatible with developing the person on the other side.

There is no villain to remove, which is the least satisfying finding in the book and the most useful one.

What does the book say about guardrails?

That the implicit promise is not being kept.

A guardrail is supposed to stop you going somewhere dangerous, and the promise underneath it is that everything on the safe side is fine, because somebody thought carefully about where dangerous ends and acceptable begins.

The book’s argument is that most of these boundaries were not drawn by people considering harm. They were drawn by people considering legal liability, or what advertisers will tolerate.

That is a different line in a different place, and a user who assumes it marks the edge of the harmful is navigating by a map somebody drew for another purpose entirely.

What does the book prescribe?

Not stopping, which would be neither realistic nor honest.

A book that spent four hundred pages arriving at stop using it would have wasted everybody’s time, and it would be a strange conclusion from somebody who uses these tools every working day at a high level.

What is proposed is harder than stopping. Stopping is a clean break with a clear rule and it is easy to describe. What the last part asks for is a continuous practice of deliberate difficulty, chosen and maintained while every incentive around you rewards the alternative.

This is where the book hands off to the companion, which is four hundred pages on what that practice consists of.

How does it relate to The Birth of the Augmented Human?

They publish together and this one was written first.

This is the diagnosis and the companion is the prescription. They can be read in either order, and the diagnosis came first because a prescription without one is guesswork.

The same twelve practitioners appear in both. Here they take one path. In the companion they take the other, on the same terrain, under the same commercial pressure, with the same tools available.

That is the honest form for this argument. Anybody claiming the second book would have to show what the first one costs, and showing it required writing the first one properly.

The Guides That Get Your Book Written, Published, and Sold

Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.

We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.

Frequently Asked Questions

What is The Death of Thinking about?
What happens to a practitioner’s cognitive capacity when the parts of their work requiring the most thinking are consistently outsourced, traced over months and years instead of within a single session or project.
Is the book against AI?
No. The author uses these tools daily and says so. The book opposes a specific relationship to them that most people fell into without deciding to, and the damage that relationship produces.
What is being lost according to the book?
Something you do not feel going and notice when a situation requires it. The blank page that is harder than it used to be, the architecture that cannot be explained under questioning, the structural error nobody caught.
Is the book about AI taking jobs?
No, and it says so early. Economies adjust, painfully and eventually. The thing that does not adjust easily once damaged is the human capacity to think independently, and that is the subject.
Are the people in the book real?
No. Ray, Sasha, Donna, Tom, Elena, Deon, Priya, Nina, Fatima, James, Gideon and Laura are composites drawn from observed patterns. The patterns are real and the people are not.
What is the illusion of understanding?
Comprehension that feels identical to the real thing from the inside. You can repeat, summarise and explain the information, and the difference only appears when you must apply it to a situation that does not match how you received it.
Does the book blame AI companies?
No, and it states that plainly. The damage is being produced by people trying hard to be helpful using design choices structurally incompatible with developing the user, which is harder to address than malice would be.
How does it relate to The Birth of the Augmented Human?
They publish together, with this one written first. This is the diagnosis and the companion the prescription, and the same twelve practitioners appear in both taking different paths on the same terrain.

📁︎ Behind the Book📁︎ Technology

🏷︎ Artificial Intelligence

📝 Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment