# On Speed, Stupidity, and the Absence of Thought There is a widespread belief that intelligence means quickness. This is wrong. It is also a dangerous belief, and we should say so plainly. A machine that generates code before you finish describing the problem is not intelligent. It is fast. These are not the same thing. A fast answer to the wrong question, or a fast answer that happens to be right for the wrong reasons, is still stupid. It merely arrives at its stupidity quickly. Let me be concrete. You have a problem. The machine produces a solution in seconds. You approve it because you are tired, or because you trust the machine, or because the solution looks plausible. Three weeks later, real people encounter the error. Money is lost, or time is wasted, or something worse happens. Now you must account for this. And here we reach the essential question: Who was responsible for accepting an answer before understanding the question? The answer is not the machine. Machines have no responsibility. They have no judgment. They cannot decide that a problem is worth solving badly, or that speed is worth more than correctness. A machine cannot betray you because betrayal requires intention. The person who signed off on the code made a choice. Perhaps they made it unconsciously. Perhaps the pressure to move quickly was so constant that the choice felt automatic, not like a choice at all. But it was still a choice. This is where wisdom enters, and where our current arrangement fails completely. Wisdom is not the same as intelligence. An intelligent person can solve a difficult problem quickly. A wise person knows when a problem should not be solved quickly. A wise person knows the difference between a problem that admits of speed and a problem that demands patience. A wise person asks: Why are we in such a hurry? Who benefits from this hurry? What are we willing to break in order to move fast? These are not technical questions. You cannot answer them with data or clever reasoning. You must answer them with judgment, which means you must actually think about them. Thinking takes time. It is boring. It produces no output you can measure. It is often uncomfortable. The machine is not the problem. Speed is not the problem. The problem is that we have organized our work in such a way that no one is required to think anymore, and we have called this progress. Here is what accountability means: It means that someone—a person, not a system, not a process—must be willing to say: "I knew this was wrong. I knew we were moving too fast. I approved it anyway. I am responsible for what happened next." This is intolerable to modern management. It is far easier to say the machine made an error, or the system failed, or the pressure to ship was too great. These things may all be true. But they do not relieve anyone of responsibility. They reveal it. The only sensible rule is this: Do not use a tool before you understand what it does. Do not accept an answer before you understand the question. Do not approve code you have not read, even if reading it takes time. Especially if it takes time. Someone decided that speed was acceptable. Ask them why. Ask them who will pay when the speed produces catastrophe. Ask them whether they would accept this arrangement in a bridge, or an airplane, or a hospital. If they would not, then they do not actually believe what they are saying. Intelligence without wisdom is merely a faster way to make mistakes. We are making them now, at scale, and we are calling it innovation. It is not. It is stupidity dressed in the language of progress. The only antidote is to think clearly about what we are doing and why. This cannot be automated. It cannot be rushed. It must be done by a person who is willing to say no.