What’s in the box?

As we’re reading and writing fewer lines of code, there’s a<br>collective feeling of dread . You just know something’s<br>missing. Where’s that sense of click when types match or that<br>pride when the code becomes the documentation?

Coding agents are pretty good at “getting the job done.” What if the<br>“job” was never the code, but the understanding you earn by writing it?<br>What if engineering an idea into code were itself the outcome to<br>appreciate? Quantum has these properties (for now); you<br>can go wild designing algorithms no machine can usefully run yet. That<br>means you can wallow in code.

So, where do you start? Don’t make my mistake… I started reading<br>papers and they skip over the “fun” parts!

After getting stuck on a JEPA-esque prototype, I went<br>deep into quantum: wrote a few research papers (QCE 2026 accepted, POPL<br>submitted, Quantum drafted), applied for a Unitary Foundation microgrant, and<br>got an opportunity to present a tutorial<br>at IEEE Quantum Week 2026.

For those who can’t make it to Quantum Week this year, I’ll be<br>uploading slides and speaker notes every Tuesday: Introduction to<br>Quantum Oracle Engineering.

Now enrolling!