Things I was wrong about.

The long write-ups, kept off the project pages on purpose. A project page should say what a thing is and let you use it. This is where the measurements go — including the ones that contradicted what I believed when I wrote the code.

Posts

7 posts

  1. Finding the PHP versions in your repos that need the php2shell fix

    How to find every PHP version your repos declare for CVE-2026-109618 and CVE-2026-109619, and which ones need the fix. In 10 public repos, 111 of 112 labeled declarations could not prove which PHP build runs.

  2. A Terminal-Bench task frontier agents could not pass

    Six runs of Claude Opus 5.5 and GPT-6 Sol scored 0 on a PDF redaction task I wrote for Terminal-Bench. Each agent tested its own work and believed it had passed.

  3. One ESP32, eight spools, two legs per filament move

    ESP32 firmware driving eight filament spools for a Bambu Lab printer over MQTT: two sensors per move, a shared TMC2209 step bus, and why unloading needs both.

  4. Putting a static site on Cloudflare Workers

    A Worker in front of static assets buys you things a static host cannot do. Here are the four config decisions that cost me the most time getting there.

  5. Driving a Bambu Lab printer over MQTT

    What an A1 mini will actually let you do over its local MQTT broker, which parts are confirmed against hardware, and which are still a guess.

  6. I could not understand Express, so I wrote my own

    Middleware chaining made no sense to me, so I rebuilt it in C++. A year later the profile said the slowest thing was a map I rebuilt on every response.

not written up yet

Open threads

Things currently unresolved in my own code. They are on the project pages as caveats; they get a post when they get an answer.

  • ams-x

    The spool module is a human right now. TMC2209 next, and the swap timing is worth a write-up once a motor is doing it instead of me.