3 posts on Go.
Notes on the twin pain of a serialized Python object that refuses to come back to life, and a Go program that wants a library nobody has written.
The architecture behind the Go client, local socket, encrypted cache, async refresh, vault-outage fallback, and the canary rollout that caught the bugs.
Why I stopped shipping Python to 9,000 Linux servers, what static linking buys at fleet scale, and how a stripped Go binary beat the container it replaced.
