The metaprogramming trick for defining a set of methods at once is useful, but I wish there were a more compiler-level solution to sorting out ambiguities or determining what's more "specialized".

These don't really color my view on multiple dispatch, however. I find it to be a really useful tool and I don't run into dispatch issues very frequently. If you're meticulous about your typing it's usually easy to avoid these pitfalls, but sometimes they still crop up.

You can't tell students anything, you have to show them, and you have to know where to start when you show them. Sometimes this meant starting back in the prerequisites to the course (a brief refresher on ODEs) and sometimes it meant arguing by anology before returning to the topic at hand.

- They have a 50% chance of measuring in the correct basis and re-sending the proper qubit - They have a 50% change of measuring in the incorrect basis, in which case their measurement means nothing and the qubit they send is in a superposition in the correct basis, leading to a chance Bob measures the wrong value

Over a very long string, it becomes exponentially unlikely that the MITM could guess the proper basis and then re-send the proper qubit to Bob. As that binary string grows in length, it's essentially impossible to MITM with any meaningful likelihood.

I suspect starting from TikZ proper would make some of the wiring easier; there's a lot of naming nodes and connecting between them that seemed unintuitive, and like I always missed an easier way to draw a circuit.

For photo editing, the interactions with the photo directly require fine control in two dimensions with the cursor.

Many GUIs are just interfaces to modal switches, or a categorical variable with usually a finite number of options.

I understand the title is technically correct, and the field of quantum error correction (and error correction in general) encompasses the detection of errors as well as the correction of them. However error detection and error correction are different (but highly related!) problems, and there are are a variety of codes that are good at each. They tried out one error correcting code, and one error detecting (in this instance) code.

It's very cool to see the surface code put to use, and I've always found it intriguing how quantum computer design is motivated by the topology of the underlying error correcting codes. There's a similar proposal for ion-trapped quantum computing where you use a 2D array of trapped ions, rather than a single linear chain, to represent your qubits. You then use different atomic ions for your logical vs error correcting qubits, and you need some different fundamental operations than you do for interactions with a linear chain of ions.

In the last six months I switched jobs into one that's more demanding of my time and mental efforts, and my gaming volume dropped significantly. I haven't booted any of the multiple-hours-per-day games I got into for the last couple of months.