How to learn quantum computing (without a math or physics degree)

Do I really need math to learn quantum computing?

Depends what you mean by learn. To build a quantum computer, sure, the math gets heavy fast. Linear algebra. Complex numbers. Eventually some group theory. To understand what a quantum computer is doing, though, you can get surprisingly far with nothing beyond high school algebra. That's what this guide is about.

I spent about a decade working through Nielsen & Chuang, which is the graduate textbook most physicists learn quantum computing from. I got good at the algebra. It didn't give me intuition. What gave me intuition was a professor at Berkeley sketching a sphere on the whiteboard and saying “the qubit is a point on this. Now watch what happens when I rotate it.” That's the approach below.

The four-week path

An hour a day for four weeks. Adjust up or down depending on how much time you have. If you blow through week 1 in a day, good.

Week 1: one qubit

The only thing you need to internalize in week 1 is the Bloch sphere. A qubit is a point on the surface of a ball. The top is 0. The bottom is 1. Everywhere else is some blend of the two, and that blend is what “superposition” actually means. The whole abstraction sits on this one picture.

The other thing to nail down: three verbs. You can preparea qubit by pointing it somewhere. You can rotate it with a gate, which is what “applying a gate” physically means. You can measure it, which snaps the point to the nearest pole with a probability that depends on which side of the sphere it was on. If you can do those three things, you can do quantum computing.

This is also the week where a physical qubit like Qubi earns its keep. I can describe a Bloch sphere in words for the rest of this guide, but nothing I write is going to match tilting one and watching the colors move. That's not a sales pitch, it's the reason we built the thing.

Week 2: two qubits and entanglement

One qubit is just a sphere. Two qubits is where things get actually strange. The word you'll hear is entanglement, and the short version is: two qubits can share a state that neither one has on its own. Measure one, and you immediately know something about the other, no matter how far apart they are. That sounds fake. It isn't.

Try this. Start with both qubits in state 0. Put a Hadamard gate on the first one. Follow it with a CNOT gate from the first to the second. You've just made a Bell state, which is about the simplest entangled thing you can build. Now measure them both. You'll get 00 half the time and 11 half the time, and you'll never get 01 or 10. Run it a hundred times. Same result.

If that correlation bothers you a little, good. It bothered Einstein for thirty years. Aspect, Clauser, and Zeilinger spent their careers proving it's real and picked up the 2022 Nobel Prize in Physics for it. The experiment they won it for is called the CHSH inequality test, and it's literally something you can replicate with two Qubis on a kitchen table.

Week 3: one actual algorithm

Pick one algorithm and work through it by hand. I'd start with Grover's search. The reason I like Grover's for a first algorithm is that you can actually watch it work. Each iteration, the amplitude of the correct answer grows and the wrong answers shrink, and if you plot it you get a nice sinusoid. The whole thing maps cleanly onto the Bloch sphere, which is why it was week 1.

If you're feeling ambitious, peek at Shor's algorithm. Don't try to understand the full proof. Focus on the quantum Fourier transform and why it hands you back the period of a function. Everything else in Shor's is number theory, and you can look up the number theory when you actually need it.

Week 4: run it on real hardware

Most self-learners stop right before this, which is a shame because it's where things get fun. Both IBM and IonQ let you run jobs on their real quantum computers over the cloud, for free. Make a free account, write the Bell-state circuit from week 2, submit it, and wait for the results to come back. Usually a few minutes in the queue.

Your histogram is going to look wrong. You'll get 00 and 11 most of the time, like you're supposed to, but you'll also get 01 and 10 a few percent of the time, which the math says should never happen. What you're seeing is noise. The qubits lost coherence, a gate fired at a slightly wrong angle, something in the environment nudged them. That's why quantum computers are hard, and it's why error correction is a research field.

Resources I actually use

There's a mountain of quantum learning material online. Most of it is either a research paper or a breathless press release. Here's the short list that holds up.

• How Qubits Work is our interactive guide to the five main physical implementations. Good for getting past the “wait, what is this thing?” question in about fifteen minutes.
• Our quantum computing glossary covers 22 terms in plain English. Use it whenever a textbook throws jargon at you.
• Quantum Country, by Andy Matuschak and Michael Nielsen, is a web essay with spaced-repetition flashcards baked in. The best free introduction on the internet if you're willing to do a little algebra.
• IBM Quantum Learning is free, deeply technical, and written by the people who build the hardware. Use it after you have intuition, not before.
• And Qubi, the physical qubit this whole guide is built around. Made by the same team that wrote it. I'm biased, but if you're the kind of person who learns better by touching things, this will save you months.

Mistakes to skip

Four things I've watched people do that just delay learning:

1. Jumping into Shor's first. Shor's is famous because it breaks RSA, not because it's a good first algorithm. The math is brutal, you'll bounce off it, and you'll conclude quantum computing is too hard. Grover's first.
2. Memorizing the gate symbols. X, Y, Z, H, S, T look like a random grab bag of letters. They're all rotations on the Bloch sphere. Once you know what rotation each one does, you never need to memorize anything again.
3. Thinking a quantum computer is a parallel computer. This is the single most common misconception and it's wrong. N qubits can represent 2^n states at the same time, but when you measure you get exactly one answer back, randomly. The trick isn't parallelism. The trick is arranging for the wrong answers to cancel each other out so the right answer is what you measure. That's called interference, and it's the entire game.
4. Reading Nielsen & Chuang first. It's the best reference textbook in the field. It is also written for graduate students who already had a year of quantum mechanics. Come back to it once you have intuition. Not before.

Who this is for

If you're a software engineer who keeps hearing “quantum computing will change everything” and wants to know whether that's real, this path works. Same for a curious high schooler or a teacher putting together a unit. About thirty hours of focused time and you'll know enough to call BS on most press releases.

If you're going for a research career in quantum information, this is a starting point. You'll still need the textbook, the linear algebra, and the patience. Nobody gets out of doing the math forever. You can just put it off until you have something concrete to anchor it to.

One last piece of advice. The single fastest way to cut the learning curve is to stop reading about qubits and start touching one. That's the reason Qubi exists.