Changes coming to Daily bit(e) of C++

First of all, I want to thank you for following the series.

Why change?

• If you have been following the series for a while, you might notice that I’m slowly reaching the point where I have written about every current C++ feature.

• The series spawned originally from my posts on LinkedIn and Twitter, where I maintained parity between the media. When I started the series, it was across Mastodon, LinkedIn, Medium, and Substack, maintaining the parity of content across all the media. This meant a 500-character limit (imposed by Mastodon). While this constraint was great for distilling critical information, it also made writing content about some C++ features impossible.

• Life is change.

What is changing?

• The main thing that is changing is that you will start seeing “reposts” of older content.

• I put “reposts” into quotation marks because I’m removing the 500-character limit. I will only repost content that I can expand on meaningfully while keeping it bite-sized.

• This creates an obvious problem for Mastodon. I don’t have a solution in mind yet; I might move to a different server (that doesn’t have the 500-character limit).

• I’m also considering what to do with Substack, but I don’t have any specific plans yet. Naturally, if I decide to make a change on a specific platform, you will get a heads-up.

• You might also see other (unannounced) experiments throughout the year.

What will not change?

• The daily cadence for the email subscribers (Medium/Substack) is not changing.

• The content will remain bite-sized.

• The series will still be strictly about C++ (and the related engineering topics).

If you made it here, thanks again for following, and as always, I’m happy to hear any feedback you might have. 😊

---