Just writing an update to let subscribers know of a new blog post. I posted a writeup of a delightfully cursed bug that we ran into and eventually ran down at work. Here it is: https://blog.nelhage.com/post/a-cursed-bug/
As a newsletter subscriber bonus, here’s some photos of Ranger. He recently saw his first-ever snow, and LOVED it. And he had a very restful snoozle thereafter.
I’ve gotten people asking which posts I decide to send to the newsletter vs posting on blog.nelhage.com. There isn’t a super crisp distinction right now, but insofar as there is, it’s something like: - blog.nelhage.com gets posts I’m confident I’ll want to be able to link to indefinitely, and/or regard as a bit more polished or considered - The newsletter is for posts I regard as a bit more “thinking out loud” or “works-in-progress,” where I’m less confident in them.
Of course, sometimes newsletter posts go viral like the previous one on Kubernetes did, and then I get a bit annoyed that I don’t have analytics or control the archive page branding. So I might change that up in the future.
I’m going to continue emailing announcements about the blog posts to the newsletter, in case you prefer to subscribe only via email. If I hear requests to do otherwise I could consider a different scheme.