The big posts type debate - Trying to get your publishing setup optimised so you can publish unincumbered is quite a challenge. It's likely different for everyone. I thought recently that I'd found a good setup. Short posts, broadly similar to Mastodon posts, linkblog posts which are short and specifically point to one resource via a URL, and blog posts. I also by the way have newsletter posts and podcast posts but these are much less frequent.
Anyway this morning I'm reading back through what got auto-merged and published using my daily merge workflow and two things jump out. First off, so many darn spelling mistakes. It's embarrassing, but with these silly virtual keyboards and if I'm in a rush, perhaps I don't have my glasses, whatever, loads of tiny spelling mistakes creep in. The other thing is that the 3 notes I published yesterday quite clearly could have been blog posts instead of notes.
It's annoying because I feel like I should be posting more blog posts, and the notes are definitely helping me to post more, but if they are blocking me from writting blog posts then that's an issue. The reason blog posts are more difficult is that they are currently more effort. I have to write a post description, and come up with a title. The only reason I have a description is because currently the RSS feed doesn't incude the full text of the post, only the description. I want to include the full text, but it's complicated because I don't know how to do code syntax highligting in RSS feeds, so I'm just avoiding the whole issue by only including the description.
Oh gosh so many small issues arise when you are building while using a piece of software. It feels like I'm so close to having it right, yet in practice I'm quite far away. Yeah this post could probably be a blog post, but now that I've written it, moving it to a blog post is going to take too much time. #