Skip to article
← BACK TO DISPATCH
A column of identical unmarked leather cases with the top two cleanly lifted and slid aside in sequence, exposing the underlying layer, the full column dominating the frame's right half.

A reversible installer for your CLI config

Every CLI installer I've ever run leaves a question hanging: what exactly did it touch, and can I get back? I've been burned enough times (clobbered configs, mystery overwrites, a setup that "worked" until the moment I tried to undo it) that reversibility stopped being a nice-to-have. It became the first constraint I wrote down.

Three rules. Back up every existing file before touching it, timestamped, no exceptions. Run it twice. Nothing compounds. And the uninstall path lives beside the install. Documented, tested, not buried in a footnote nobody reads until it's already too late.

The minimum viable floor I'd actually ship: two hooks. One that blocks secrets from reaching a commit. One that blocks bypassing that check. Those two catch the failures that actually cost you.

Package the whole thing as a tarball. What you see is what installs. Honest handoff.

Whether this is the right shape for every situation, I'm less sure. But it's the one I wasn't nervous to hand over.

Get the next dispatch when it drops.

SUBSCRIBE FOR THE NEXT DROP MORE ARTICLES