The library that appointed itself signal handler
A commit landed a month before I noticed it. By the time somebody told me, two of my own tools had already written workarounds for it without mentioning it.
Tags
6 pages
Abstraction
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.
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.
Posting unifies, tokens don't
One interface posts a reel to four platforms cleanly. Their OAuth token handling refused to unify at all, which is why I built all four first.
