The component that fired on every schedule
A CI component gated on the default branch fired on every Renovate schedule too, because a scheduled run is also on the default branch.
Categories
121 pages
Pioneering
Notes from active builds: the design decisions, war stories and how-it-works of whatever I'm making right now.
The grid that would not behave
A desktop-first photo tool reviewed mostly from a phone, and the CSS grid that refused to behave on the one screen it was being judged on.
Stop installing the same tools on every pipeline job
Nearly every CI job began by fetching and compiling the same tools. Baking them into one image instead, and what that saved per pipeline.
The scaffolder that won't hand you code that doesn't compile
A Rust scaffolder with an AI codegen path that drafts a real command, then refuses to hand it over until it compiles and passes lint.
About that 'no AI'...
A correction to my own post: the culler does contain machine learning, and the distinction I drew between ML and AI does not survive scrutiny.
The afternoon the agent earned its keep
Adding stream-copy remux to a WebAssembly FFmpeg build, where writing Matroska hung forever and the identical MP4 path did not.
You can't reshoot a wedding
A photo tool that is non-destructive by construction rather than by intention, because the shoot it works on can never be taken again.
The build gate these sites never had
Three Hugo sites each hand-rolled a near-identical deploy job that only ever ran on merge, so nothing ever checked the build before it landed.
The secret that wasn't on my branch
A secret scanner failed a merge request over a test key and a documentation PEM that the change did not contain. Scoping a scan properly.
I filed a feature request into my own framework
Building on your own framework means finding its gaps as a user rather than an author, and having to file the request against yourself.
