How this site is made

What gets listed, how the code is checked, where the money comes from, and what this site will not publish. Written so you can tell the difference between a judgement and a fact.

Who writes it

Dr. Donovan writes and maintains everything here, and Dr. Donovan also writes on quantum computing research, hardware and industry at Quantum Zeitgeist, which is a separate publication he contributes to rather than one he runs. There is no editorial board, no panel of reviewers and no guest contributors. One person is accountable for every page, and the byline says so.

What gets listed

The catalogue holds 87 courses across 13 platforms, of which 51 are free to take. A course is listed when it exists, is reachable, and teaches quantum computing or a prerequisite for it. That is the whole bar. It is deliberately a low one, because the useful work is describing accurately what each course covers and who it suits, not gatekeeping a list.

Descriptions are written from the syllabus and the course itself, not copied from the provider's marketing page. Where a course assumes maths or programming you do not have, the page says so. Where a course is outdated, it is either marked or removed rather than quietly left to rot.

What this site does not publish

There are no star ratings on course cards, no review counts, no aggregate scores and no testimonials. This site has not run those courses through a scored assessment, so publishing a number would be inventing one. A build check fails if rating or review markup appears anywhere in the structured data.

There are also no claimed certifications, accreditations or endorsements. Where a course leads to a real credential, that credential belongs to the provider and the page names the provider.

How the code is tested

The 220 tutorials exist because tutorial code that no longer runs is worse than no tutorial. Every runnable snippet is executed before publication by a script in this repository, and the snippets in one tutorial share a single execution context, so a variable defined in the second block still has to work in the ninth. Blocks that need paid hardware access are skipped individually rather than exempting the whole file.

This does not make the tutorials permanently correct. Qiskit, Cirq and PennyLane break things between versions, and a snippet that ran in February can fail in August. It means the code ran against the stated version on the stated date, and that reruns are cheap enough to happen.

Reference material

The 26 framework references and the 241 glossary entries carry the version they describe where a version applies. The framework popularity comparison uses figures pulled from public repositories and states both what it measured and when, because a star count without a date is a number with no meaning.

How this site makes money

Links to paid courses are affiliate links, so a purchase made through one earns a commission at no extra cost to you. The site also carries advertising. Neither affects what is listed or how it is described, and the clearest evidence of that is that 51 of the 87 courses are free and earn nothing, and that free alternatives are named on pages about paid courses. The full terms are on the affiliate disclosure page.

Dates and corrections

Articles carry a publication date, and the structured data carries a modification date when a page has been revised. Neither is decorative and neither is bulk-set to make the site look freshly updated.

Content gets removed when it cannot be supported. In June 2026 the case study library was cut from 138 entries to 34 because the rest could not be traced to a primary source, and that reduction is recorded in the repository rather than quietly absorbed.

If something here is wrong, broken or out of date, write to hello@quantumcomputingcourses.com. Factual corrections get made and the page's modification date changes with them.