Show HN: Learn quantum programming in short, simple lessons
demo.quantumlab.cc
Show HN: Learn quantum programming in short, simple lessons
1–9 of 9 posts
Re: Show HN: Learn quantum programming in short, simple lessons
#2The presentation isn't great either. Why do I need to click on a next button every sentence?
I also don't feel like I learnt anything meaningful from the Fundamentals tutorial.
Re: Show HN: Learn quantum programming in short, simple lessons
#3Re: Show HN: Learn quantum programming in short, simple lessons
#4I went through the intro. The Python exercises are flakey. Most of them didn't do anything when I clicked Run or Submit. I messed around and called the function myself and that seemed to get it to start doing something. The presentation isn't great either. Why do I need to click on a next button every sentence? I also don't feel like I learnt anything meaningful from the Fundamentals tutorial.
We wanted to start with very simple concepts for the demo to validate if there is interest in this direction and it makes sense to work further.
Re: Show HN: Learn quantum programming in short, simple lessons
#5Re: Show HN: Learn quantum programming in short, simple lessons
#6Minor point - I think that your lessons under Fundamentals 1 (I) are in the wrong order. It starts with the second lesson (2. Qubits).
Re: Show HN: Learn quantum programming in short, simple lessons
#7Re: Show HN: Learn quantum programming in short, simple lessons
#8Re: Show HN: Learn quantum programming in short, simple lessons
#9https://demo.quantumlab.cc/courses/1/2
I don't think this is a good description of the expected output:
The function applies a Hadamard quantum gate to the supplied qubit and measures it.
Returns: A tuple of two objects representing an application of Hadamard and measurement gates on each qubits.
The description refers to the "supplied qubit", but there are no parameters.
The expected return description mentions "each qubits", but there is only one qubit to be processed.
Last, the expected return is described as "a tuple of two objects", but actually it expects the returned object be of MeasurementGate type.
This code was considered valid:
q = GridQubit(0, 0)
q = H(q)
result = measure(q)
return result