Skip to main content
Think about the difference between a thermostat and a senior engineer on call. A thermostat is pure specified behavior. “If temperature < 20°C, turn on heat.” It is deterministic, auditable, and dumb in the precise sense that it has no notion of why. Given the same reading it always does the same thing. You trust it completely — within its tiny domain — and you would never ask it to do anything else. A senior engineer on call is something else entirely. You hand them a vague, novel problem (“checkout latency is up, figure it out”) and they draw on a vast fuzzy memory of ten thousand past situations to produce a plausible course of action. Ask them the same question on two different nights and you may get two different first moves, both reasonable. They can be brilliant. They can also be confidently wrong, especially when the situation resembles something they have seen before but isn’t actually the same. You do not trust them blindly — you ask them to explain their reasoning, you keep a change log, and for irreversible actions you require a second pair of eyes. Modern AI is far closer to the second thing than the first. It is pattern-matching at enormous scale, producing plausible outputs from fuzzy memory. The entire discipline of this docs is learning to get the brilliance of the on-call engineer while installing the guardrails — the change log, the second pair of eyes, the explain-your-reasoning — that make it safe to put in the loop. Hold the analogy loosely. AI is not a person and does not “understand” the way a person does. But for building intuition about how to operate it, “a tireless, fast, slightly overconfident colleague with an encyclopedic but imperfect memory” is a far better model than “a very clever thermostat.”
Last modified on June 8, 2026