Lover of mirth and gaiety. Server-side engineer working on distributed systems & cloud infrastructure (Nix, Go, & k8s). Avid home-labber; compiler-head.
Self-identified as one who uses their eyes to feel. Believer in all things drab and yellow. Man possessed of a sallow visage; remember: “it’s a secret to everybody!” All thoughts are mine own.
A local development environment is usually a set-and-forget affair (until something breaks, anyway). Mine had accreted for years across two machines and two operating systems, and the state of each was known only to whichever shell history survived last. So I rebuilt the whole thing declaratively with Nix, and I have been enjoying the process far more than I expected to.
Go’s structured logging library (log/slog) is quite the clever piece of standard library code. This is thanks to the processing of log attributes {key:value} with zero heap allocations. And despite the slog.Logger interface (inspired by packages uber-go/zap and rs/zerolog) now long being the go-to idiom for any generic logging use-cases in Go; it is additionally highly-optimized for use in application hot-paths.