Blog
A post hit Hacker News and the analytics showed pages far heavier than a static site should be. The cover images were the payload.
A dozen agent sessions running at once is not a capacity problem. Working out which of them is stuck is, and the obvious way to find out is the wrong one.
FFmpeg assumes a disk it can seek around in. Giving it a convincing in-memory filesystem, and testing the behaviour that would hurt most first.
I run a coding session per repository and they can't talk to each other. For a while the thing carrying messages between them was me, and I kept getting it wrong.
Three HIGH advisories deep in a Rust dependency tree, a one-line fix that changed nothing, and eleven minor bumps that were never mine to make.
I put my working practice on a public shelf, and then took some of it back off again. Working out which half was the interesting part.
afmpeg shipped single input to single output. Adding multi-pad filter graphs and multi-output muxing: one decode, two files, one pass.
A browser will not attach a bearer token to a page navigation. Swapping the header for a cookie the framework already understood, without weakening it.
Half my CI jobs ran for no reason on every merge request. Skipping them with rules:changes, and why that is trickier than the manual suggests.
rust-tool-base needed go-tool-base's control over which commands an AI agent may call. Closing the gap meant doing the opposite of what Go did.
Pioneering
Campfire
afmpeg
cicd
rust-tool-base
ffmpeg-wasi
keryx
