You Don't Need to Know How It Works — And That's Exactly the Problem

Source: Dev.to

Introduction

This is not a post about AI. It is a post about what happens to people who never ask why.

I was at a protest when someone told me the internet should be a human right. He was holding a four‑thousand‑pound laptop, coffee in one hand, earbuds in, passionate, articulate, certain. I asked him what the internet actually is.

He described Facebook, YouTube, speaking to friends. I said: that is the World Wide Web. What is the internet? He looked at me, then said: what is the World Wide Web? I got scared—not because he did not know, but because he was screaming about a thing he had never once tried to understand.

What the Internet Is

The internet is infrastructure: physical cables, servers, routing systems that cost billions to build. The World Wide Web sits on top of it. The web is the passenger; the internet is the road.

None of this is complicated. It takes about ten minutes to understand, but most people who depend on it daily have never spent those ten minutes.

Design and Dependency

The gap between using something and understanding it is becoming one of the most dangerous gaps we have, and we are widening it deliberately—not through malice, but through design.

• Think about the person who has never changed a tyre. The tools are in the boot; they came with the car, but the person has never been curious enough to try.
• The phone you are holding is not a phone. It is an attention system, engineered to be as frictionless as possible—not for your benefit. Friction creates conditions for thought, and thought creates conditions for demand, and demand is expensive.

The easier a tool is to use, the less you need to understand it. The less you understand it, the more dependent you become. The more dependent you become, the more useful you are to the people who built it. That is not a coincidence; that is a business model.

AI and Judgment

I have heard tech leaders say you no longer need to think for yourself, that AI will do it, that coding will be irrelevant by the end of the year.

I want to be precise. A large language model predicts the next word based on patterns in human text—extraordinarily capable, but not thinking. The distinction matters because the people telling you AI will replace your judgment are often the same people who benefit most from you believing it.

The more a technology is positioned as inevitable, the more urgently you should ask who benefits from that inevitability feeling settled. This is not paranoia; it is the minimum condition for being a free person in a technical world.

The Cost of Simplicity

Every time we optimise for engagement over understanding, every time we make a product simpler in a way that removes agency rather than friction, we are widening the gap.

There is a difference between removing unnecessary complexity and removing the conditions for thought. Most of us have stopped asking which one we are doing.

The real question is not: does this product work? It is: what kind of relationship does this product create between the person using it and their own capacity to question the world? Most products being built right now are answering that in one direction—toward dependency.

Conclusion

The man at the protest was not stupid. He was the product of a system designed to make understanding unnecessary. We built that system; some of us maintain it every day.

So the question is not whether your users understand what you are building. The question is whether you have ever stopped to ask if you want them to.

This is an adapted excerpt from a longer essay on dependency, digital literacy, and what shared leadership demands of tech builders. The full essay is here.