Clearly OT but the excessive reliance on foo and bar in many of my early C lang learning examples really slowed down my ability to transfer said techniques into something meaningful. Eventually one of my friends working in the Visual C++ team (I'm dating myself here) explained the connection of foo and bar to fubar and kind of felt like this!
I had the same experience; that's mostly what I'm referencing. Trying to use things like The Hacker's Dictionary (largely in-jokes, bad jargon, and obnoxious circular definitions) to clear it up made the problem worse. I get that it's just a humor book, but still.
You're right, the essay needs a better explanation on what a ket and a quantum state is. I'll figure something out.
Excellent point with the superposition, I'll add that in! Same with the normalization - while adding the `is_valid` method to the struct makes sense programming story -wise, it'd be great to justify its origins and implications.
As for using Rust being pointless - I am writing this blog post series for three reasons: learning more Rust by doing, learning more quantum computing by doing, and sharing my journey as a tutorial. Using Rust for the sake of learning (and hopefully helping others learn) Rust is in my opinion a perfect reason to use Rust.
As for calling this QC - I'd clarify that this code does not intend to be a production-grade QC library, and the blog post series does not intend to be an exact, axioms-and-proofs type of an university level course that prepares you for the industry in one go. I'd think of it more as a Todo MVC app building journey with a quantum flavor - or something. That being said, I do plan to add more QC features in the next posts of the series, and incrementally add to the accuracy as much as I feasibly can. All this feedback here and links to more materials are helping me immensely, I want to learn more about this stuff!
Thank you for calling it very cute - I really appreciate that! ️