Ask

newsletter or just a public changelog when i have 3 hours a week to write

Changelog first, and let the newsletter be a byproduct rather than a second job.

The mechanic that worked for me: write the changelog entry as part of shipping, one paragraph, in the PR description, and have it end up on the public page. Once a month, take the four or five entries, add two paragraphs of context at the top about what you are trying to do and what did not work, and send that as the email. The writing was already done - the only new work is the framing.

Weekly newsletters die because 3 hours a week is 3 hours in a good week and 20 minutes in a bad one, and one missed week turns into three. Monthly survives a bad month.

163 · in/build-in-public ·