Keeping changes from two musical experiments
Compare four recordings of a Burgmüller passage, switching accompaniment deletions and shorter melody notes separately or together.
Eigenvalues / Long-form writing
Essays
Building a tool around eight bars of music, making its changes readable, and carrying experiments forward. These essays follow what I build and the questions it raises, alongside longer arguments about software and markets.
Making a MIDI diff readable as music
Change the opening note in a recorded MIDI example and compare Battuta’s musical description with its exact-identity view.
One fill, two deliveries, one ledger entry
A local Kafka experiment keeps a one-unit fill counted once across consumer crashes by committing its identity and ledger effect in the same database transaction.
The eight bars I built a MIDI tool around
Hear the eight-bar MIDI file that led me to build Battuta, a tool for inspecting, changing and comparing music with an AI agent.
The check passed because it never saw the edit
Restoring a known MIDI defect left my new check silent. The broken edit controlled whether it was checked; fixing that exposed what a shared check could and could not replace.
Why the instrument change didn’t change the sound
A MIDI edit changed the file but left the sound unchanged. I kept inspection available to diagnose the missing event order, while making edits that introduce it stop for review.
Who pays for the information in market prices?
Prices can reveal information that someone paid to discover. I use that tension to examine what informed trading must earn, and where Maxwell’s demon stops helping explain it.