The standard advice is to build a content calendar. Plan a month ahead, assign topics to days, work to the schedule.
For a marketing team with a product to launch, this is correct. For a solo developer, it fails in a specific and predictable way.
The mismatch
A calendar requires knowing in advance what you will have to say.
You do not. The best material from any given week is the thing that went wrong on Wednesday, and on Monday you did not know it was going to.
So you end up with two bad outcomes. Either you write to the plan and produce generic content, because the topic was chosen before you knew anything specific about it, or you abandon the plan by week two and feel like you failed at something.
What a calendar is actually solving
Two real problems underneath it.
"I forget to post." Real. Solved by a recurring slot, not by topics assigned in advance.
"I do not know what to write about." Also real, but a calendar does not solve it. It moves the problem earlier, to a point where you have even less information.
What works instead
A slot, not a schedule. Tuesday and Thursday mornings, twenty minutes. The commitment is to the time, not to a subject. What you write about is whatever happened.
A running list, not a plan. One text file. Every time you hit something interesting, one line. Do not organise it. Do not tag it. When the slot arrives and nothing obvious happened, the file has five things in it.
A default topic. One subject you can always write about with no preparation, usually a problem in your domain you have thought about for years. On weeks when nothing shipped, you have something.
The one place a calendar earns its keep
Launches.
If you are shipping something on the 15th, the posts around it do need planning: what goes out before, what goes out on the day, what follows up. That is a real sequence with dependencies, and improvising it produces a worse result.
So: calendars for launches, slots for everything else. The mistake is applying launch-shaped planning to ordinary weeks, where there is nothing to coordinate and the plan can only reduce what you would otherwise have said.
The underlying point
Planned content is worse than reactive content for builders, because your advantage is specificity and specificity only exists after the fact.
A marketing team plans because their content is not about anything that happened. Yours is. That is the whole reason anyone reads it, and it is also why you cannot schedule it.