Blog
The job told me, very politely, that it hadn't done its job, and then exited 0. Two questions were enough to undo the spec written to fix it.
To append four lines to one YAML file, the release job was cloning this entire website into memory. The first fix for it failed without making a sound.
I wrote the process document before doing the hard one. Then the hard one went through it and rewrote a step.
Management and engineering are two sides of the same coin, and far too many companies forget the engineering side has no cap.
A model handed a bug will hand you back a plausible fix and a green test suite in about a minute. That tells you almost nothing.
Everyone writes up the modules that came out. The decisions that mattered were the four packages I decided to leave exactly where they were.
I went looking for reproducible CI images and found the builder had been archived fourteen months earlier. Swapping it out turned out to be the easy part.
Twenty-seven packages, four marks each, out of ten. The interesting column wasn't the one I expected, and one row explained the whole programme.
I read the question my support bot had fluffed, gave the correct answer off the top of my head, and was wrong. The docs had fooled the person who wrote them.
I wanted an FFmpeg that couldn't touch my disk. Building the interface to get one accidentally produced something considerably more useful.
colophon
Pioneering
go-tool-base
Campfire
cicd
afmpeg