Why I'm Going Deep on Quantum Computing (as a Builder, Not a Physicist)

Most quantum writing sits at two useless extremes. One is breathless. Every announcement is a breakthrough, every chip is the one that changes everything, and the timeline is always soon. The other is dismissive. It is all hype, none of it works, come back in twenty years.

Neither is a substitute for looking at the real thing, and neither is very useful if you actually build for a living. As an operator I do not care whether quantum is inspiring. I care what it can do today, what it costs, what breaks, and how far the real thing is from the slide. That is the gap I want to close for myself, in public.

What is true is messier and better than either extreme. There is no single quantum computer. There are several competing hardware approaches, and no one has clearly won. Superconducting qubits, trapped ions, neutral atoms, photonics, and quantum annealing are genuinely different bets, with different strengths, different failure modes, and different companies behind them.

I find that disagreement encouraging, not confusing. When serious, well funded teams still disagree about the basic approach, the field is early enough that a builder can still form a real opinion by doing the work. That is exactly the window I like to operate in.

When serious teams still disagree about the basic approach, the field is early enough that doing the work still beats reading the takes.

I do not want to write takes. I want to run the machines and report what happened.

So this series runs on two habits. The first is to track the real field rather than the headlines. I am following the companies actually building hardware, from the large players to the specialists, and paying attention to what they ship instead of what they promise.

The second is to get hands-on. Several of these providers offer real access, including free tiers. I am going to submit real circuits to real hardware, then write down what worked, what did not, what it cost, and what surprised me. When I do not understand something, I will say so plainly.

The standard is primary-source. If I tell you a backend behaved a certain way, it is because I watched it behave that way, not because a vendor slide said it would.

It will be honest about how early this is. Real runs, real numbers, real dead ends. It will keep pulling quantum back to the thing I actually know, which is building and shipping products, because the builder's lens is the only angle I can offer that a physicist cannot. My interest is not the math for its own sake. It is the question every operator eventually asks about any new platform: when does this become something I can build on, and what should I understand before it does.

It will not be a hype feed. No breakthroughs that are not breakthroughs. No pretending I have expertise I have not earned yet. No filler.

If a builder working through quantum in the open is useful to you, follow along. The next post will be the first hands-on run, on real hardware, with the numbers attached.