Go error wrapping without the head-scratching
One letter in a format string decides whether the check you wrote yesterday still works today. Here's the whole of Go's error chain, built up from that letter, with every output taken from a real run.

One letter in a format string decides whether the check you wrote yesterday still works today. Here's the whole of Go's error chain, built up from that letter, with every output taken from a real run.

Signing releases is the easy day. Replacing the key you sign with, while every installed copy is still checking against the old one, is a job I went looking for a guide to and couldn't find.

Publish an OpenPGP certificate a researcher can encrypt to, and read what they send, without a private key ever existing in your process.

Ten minutes, a throwaway directory and no cloud account, to find out what a release signature actually is before you decide whether you want one in your pipeline.

Two configs for one tool, the user's and the project's, and no rule anywhere about which one wins. Twenty minutes to make one a layer of the other and keep a straight answer about where every value came from.

Four places a config value can come from, and the only question that matters at the wrong end of an incident: which one won, and why. Twenty minutes, one module, no services.

Fifteen minutes, no API keys, nothing to pay for, and a real mp4 at the end of it. The cheapest way to find out whether keryx does what you think.

A change that ships without a version bump reaches nobody, and nothing tells you. Ten minutes in a throwaway directory to see it happen, and then catch it.
