Last year I tried to do one blog post every other week starting in march (and almost succeeded).

I did 18 posts total with the first post on March 9th averaging 15.6 days between posts (with some outliers at 40-50 days but also quite a few posts within 7 or less days between each other).

Overall I came just short of the total goal (21 posts in 43 weeks since March 9th).

Recap

While I didn’t quite reach the goal it was still a lot of fun (and also stressful).

Producing consistent content has been hard for me because I was doing it on the side and in general I tend to not blog about “old stuff I already know” but rather about new stuff I just learned or am in the process of using.

This means that even though there is a lot of “easy” stuff that I could write about, I often picked topics that I was just recently working on.

Also to produce a new blogpost I first like to invest quite a bit of time to actually use what I will be blogging about which means a blog post that can be written in 1 hour (if the subject is known) actually takes me 10-20 hours to produce because I first implement whatever I will be writting about.

Going forward

For this year I plan to do only one post per month to increase consistency. I’m aiming for the second saturday of every month as the release date.

This will give me more time for each post to refine.

Overall I want to blog more about “stuff I already know” (I barely blogged about any gamedev stuff last year despite my blogs current tagline “.Net, Azure and occasionally gamedev”).

I realised that there’s a lot of stuff I know (and take for granted) that I never talk about because I (wrongly) tend to assume that everyone knows it already.

This year I realized that my assumption was wrong (for example everyone I talked to about it learned something from me about Shells and Mklink).

While these aren’t “essentials” to using Windows or developing software they can easily improve productivity of anyone so I will probably be talking more about similar productivity stuff as well.