Publication record
About the author and publication
Who writes Quantum Computing, End to End, what the field guide covers, and how to interpret its authorship and review signals.
Responsibility
Steven Geller is a CTO with two decades of experience building and securing infrastructure, primarily in financial systems. His current technical work includes cryptographic systems and post-quantum migration.
Steven Geller writes and maintains this field guide. The named author is the accountable editor for its explanations, structure, source choices, and corrections.
The author profile describes relevant engineering experience; it does not claim an academic appointment, physics doctorate, or independent peer-review credential.
Scope
The book is written for computer scientists and engineers who want the full system: mathematics, circuits, algorithms, software, fault tolerance, hardware, applications, and diligence. It is educational material, not investment advice and not a substitute for safety, legal, or security review.
How to read trust signals
Each chapter identifies its author, publication and revision dates, chapter-level sources, and current review status. Missing independent review is shown as missing; it is never implied by visual polish.
Privacy and first-party measurement
This publication uses cookieless, first-party measurement to learn whether readers can find and finish useful material. Events include the canonical pathname, page type, chapter and part labels, coarse viewport and referrer classes, reading milestones, navigation and citation actions, artifact and audio use, search result counts, and basic loading, interaction, and layout performance.
The client does not send URL query strings, raw book-search text, article text, email addresses, or a cross-site identifier, and it does not set an analytics cookie. Search activity is reduced to a query-length range and result count. Do Not Track is honored: when the browser sends that preference, the client sends no measurement events.
Measurement is posted to this site's own /.sg/event endpoint. It is used to improve the publication's content, navigation, accessibility, and performance—not to build advertising profiles.