How to Scope a First Quantum Prototype: Requirements Before Wishes
A step-by-step method for small teams starting with quantum computing: state the question, apply a blocker test, and rank every other preference as a tie-breaker.
Quantum Experiments Need a Version History More Than Most
Hardware drift and statistical results make quantum work hard to reproduce. A look at the state of the practice and why dated experiment records matter so much.
Quantum Computing Project Pre-Mortem: A Plain-Language Guide
Quantum projects attract hope and stall for ordinary reasons. A plain-language explainer on imagining the failure first and fixing six common causes.
Quantum Projects That Freeze or Overcommit: A Reversible Fix
Quantum teams either stall or bet everything on one device. A friendly diagnosis, and five habits that keep your options open while the field changes.
Six Myths That Stop Beginners Sharing a First Quantum Experiment
You do not need hardware, a breakthrough or mastery of the maths to share a small quantum experiment. Six myths, checked against how the field works.
Keeping Your First Quantum Experiments Alive: A Beginner Primer
A beginner primer on keeping early quantum notebooks, results and reading lists working as tools change, ending with a short glossary of key terms.
Three Ways to Explain a Qubit to a Beginner, Compared
I tried to explain a qubit to my sister three different ways and each attempt found a new hole in my understanding. Here is how analogy, maths and code compare.
Eight Things Quantum Teams Remove to Get Better Results
A list of eight deliberate removals, from redundant gates to idle qubits and extra shots, that improve quantum computing results on today’s noisy hardware.
A Ten-Point Check for Quantum Explainers, Run for One Reader
A friendly checklist for auditing any quantum computing explainer against one real reader, a busy physics teacher, covering analogies, maths, honesty and length.
Cost Per Experiment: A Plain-Language Look at Quantum Workloads
Quantum experiments often run alongside ordinary cloud computing. Here is how to think about the cost of one run, one shot and one finished result.