September 2, 2026·7 min read

You can't picture a qubit, and that's the whole problem

Quantum computing isn't hard because the math is hard. It's hard because your intuition was built for a world that doesn't apply.

By Andrew Pyle

Every explanation of quantum computing starts the same way: a bit is a 0 or a 1, but a qubit can be both at once. Then someone says "superposition," someone else says "it's like a coin spinning in the air," and everyone nods. Nobody's intuition actually moved. We walk away able to repeat the sentence and no closer to picturing the thing the sentence points at. That gap — between reciting the words and holding the idea — is what this one is about.

01Why metaphors fail

Why the metaphors fail

That coin metaphor is where understanding goes to die. A spinning coin isn't both heads and tails — it's one or the other, we just haven't looked. Superposition isn't ignorance about a definite state. It's a genuinely different kind of thing, and the reason it feels impossible is that you're trying to render it with hardware — your intuition — that was trained entirely on classical objects.

I don't think the fix is more math. The math is learnable and, honestly, not that exotic — it's linear algebra with a probability rule attached. The fix is building intuition where none exists, and intuition doesn't come from equations. It comes from playing with something until it stops surprising you.

There's a sharper reason the coin does damage. A good metaphor hands you a feeling of understanding you never actually earned, and that feeling is the thing that stops you from asking the next question. Confusion at least keeps you looking. The coin closes the case — it lets you file "superposition" under "basically a spinning coin" and move on, permanently one step short of the idea. I'd rather leave someone honestly puzzled than falsely satisfied.

Classical intuition doesn't just mispredict quantum systems; it mispredicts them confidently and in one specific direction. It assumes that if you don't know a value, the value is nonetheless already sitting there, waiting to be read — the coin has landed, you just haven't peeked. Quantum mechanics says no: before measurement there is no hidden answer being concealed, and interference — outcomes canceling each other out before you ever look — only makes sense if there was genuinely nothing decided yet. That single wrong assumption, baked into every person by a lifetime of pushing classical objects around, is the thing an interactive has to dislodge.

02Turn the knobs

Build intuition by turning the knobs

That's why I keep coming back to this one as an interactive, not an essay or a video. You have to manipulate the thing. Rotate a state and watch the measurement odds change. Entangle two qubits and see that measuring one genuinely tells you about the other. Watch interference cancel a wrong answer out. The goal is to let you turn the knobs until "both at once" stops being a slogan and becomes something you can feel the shape of.

The honest surprise is that a single qubit already has a real picture — it just isn't the coin. One qubit's state is a point on the surface of a sphere. The gates a program applies are rotations of that point; a measurement reads out a probability that depends only on where the point ended up. None of that requires a metaphor, because it's the actual object, and you could drag it with a mouse. The wall — the good wall, the one worth walking someone into — is entanglement: two entangled qubits cannot be drawn as two separate spheres, and the moment you try and fail is the moment the idea finally lands, not as a slogan you repeat but as a limit you ran into yourself.

A metaphor tells you what something is like. A sandbox lets the thing tell you what it is. The difference is who's doing the talking — the explainer, or the object itself.

The reason I trust manipulation over explanation isn't a teaching theory. It's the same instinct that governs everything I ship: I trust a live endpoint answering a real request over a green checkmark that only claims it should. Understanding works the same way. You don't know a system because someone described it correctly to you; you know it because you poked it and watched it push back in a way you didn't predict. An interactive is just that instinct pointed at an idea instead of a server.

03What I do

The one thing I'm actually good at

Strip the physics away and this is a version of the only problem I'm genuinely good at: taking a fuzzy idea and making it precise enough that a machine can execute it. That's the move under everything I've built — I went from explaining other people's products to building my own, and the whole transition was learning to turn intent into a system that runs. A metaphor is intent that never got compiled. An interactive is the same idea forced all the way down to something executable, where the hand-waving has nowhere left to hide.

So the interactive isn't a detour from what I do — it's the purest case of it. Every project I run has the same skeleton underneath: a fuzzy human intention on one end, a system that actually runs on the other, and my job living entirely in the translation between them. Usually the fuzzy end is a business goal. Here it's a piece of reality that has resisted plain language for a century. Same skeleton, harder middle.

It's also why I'm not worried that I'm not a physicist. The physics I need is bounded and public — the rules are written down and haven't changed in decades. The part that's genuinely unsolved is the interface, and interface is the discipline I've actually spent years inside. The scarce skill here isn't knowing quantum mechanics; plenty of people know it cold and still can't make you see it. The scarce skill is building the thing that makes it felt.

04Earn the picture

The line I won't cross to ship it

There's a failure mode I'm wary of, and it's the reason this stays unbuilt rather than shipped fast. It would be easy to build something that looks like a sandbox but is secretly still a metaphor — sliders wired to a cartoon, an animation that feels physical but lies about what's underneath. That's worse than the coin, because it wears the costume of the real thing. I hold the same bar here that I hold for any data I publish: if it isn't faithful to the source, it doesn't ship, no matter how good it looks. A visualization that's convincing and wrong is a liability, not a feature.

The bar is what makes it hard, and the hardness is what makes it worth doing. Faithful means every knob maps to a real degree of freedom in the actual state, every measurement obeys the real probability rule, and the places the picture genuinely breaks down — entanglement again — are shown breaking down rather than quietly papered over. That's a real build, not a weekend toy, which is exactly why it's still a note in a file and not a link I can send you.

05The bet

The bet: the interface is the understanding

I want to be honest about where this sits: it's a curiosity, not a product, and it isn't built yet. I'm not a physicist. What I have is a strong belief that most quantum explainers fail for a specific, fixable reason — they hand you a metaphor instead of a sandbox — and a suspicion that the right interactive could do in ten minutes of play what a semester of hand-waving doesn't.

This one sits at the far edge of what one person can build now, which is exactly why I keep it on the list. If I can build something that makes even one piece of it intuitive — not simplified, not metaphored-away — that's a small proof that the distance between "I understand the math" and "I understand the thing" is bridgeable with the right interface. That's the whole bet of this one. The interface is the understanding. I just haven't built it yet.