Issue #1 promised “roughly once a week.” It has been twenty weeks since. This issue is the overdue explanation. The excuse is decent: the time I’d budgeted for newsletters went into the blog itself.
Ten pieces shipped in those twenty weeks. Posts, two talks, a podcast appearance.
May was mentorship month. A three-part series, one part per week: why I keep mentoring in open source, a mentee playbook for getting into LFX, GSoC and friends, and how stewardship actually works inside OpenTelemetry. Somewhere in the same month, a talk I gave at PromCon Online in 2020 was adopted into the official Prometheus documentation, which earned a short grateful note.
July went to a single dense one:
OpenTelemetry’s Go compile-time instrumentation reaching v1,
the zero-code telemetry story threaded through the toolchain’s
-toolexec hook.
August was the talk month. Why Your Go Benchmarks Are Lying and Instrument Go Without Changing a Single Line landed a day apart, and I joined Cup o’ Go to talk about instrumentation and blast radius.
Then the two personal ones, which took the most out of me: my second brain system (PARA, Readwise, and an LLM that captures my thoughts but never edits a source note), and being a late-diagnosed ADHD engineer in the age of AI agents. That last one explains a fair bit about the rest, including why the newest, least-established habit was the first thing to slip when the calendar filled up.
The Unwind is still alive. The weekly promise is retired; roughly monthly is the new honest target. Next issue goes back to the original plan: what I’ve read worth sharing and what I built. If I’d written twenty newsletters instead, I’d have nothing to link to.