The bill for fifty-one modules
Change one line in the tls module and you've signed up for twelve releases. That's not a bug in the architecture, that's the architecture.
Tags
34 pages
Architecture
The extraction playbook only got real when chat left
I wrote the process document before doing the hard one. Then the hard one went through it and rewrote a step.
The packages that didn't want to leave
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 graded every package for how badly it wants to leave
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.
The escape hatch that turned out to be french doors
I wanted an FFmpeg that couldn't touch my disk. Building the interface to get one accidentally produced something considerably more useful.
The most tempting corpus in any repository
The issue tracker is full of answers, which is exactly why my support bot isn't allowed to quote it. An issue can point at the docs, but it never gets to be the answer.
The repo that downloaded 170 gigabytes
An hour to compile and 170GB of artefacts to clean up afterwards. Rust has a built-in answer to that, and I only used half of it.
A format per module, not a fatter config core
Viper reads a dozen extensions. Mine reads one, and the other formats live somewhere else entirely. Here's what that bought, measured rather than asserted.
The writer I added, and the Viper I deleted by accident
I set out to add a config writer and keep Viper. I ended up keeping the writer and deleting Viper, and I didn't notice until it was already gone.
Config is a border, not a chain
I built a boundary so I wouldn't have to move my config package. Then I moved it anyway, and the boundary is the only reason that didn't hurt.
