Ouch... that actually hits a bit close to home. After having a couple of blogging homes fold out from under me, I've kicked around the idea of coding up my own blog - which usually was in whatever framework/language I was getting ramped up in. I realize I've probably ported/built something a half a dozen times in the last decade, and never bothered to take the final step to deploy it before starting the next rewrite.
I started writing my blogging engine [1] in late 1999, and spent almost the next two years trying to get it perfect, while at the same time using it for blogging (locally at first). I finally got fed up with trying to perfect the software and just went public with it. I still use it after 25 years. Granted, there hasn't been a line of code that hasn't changed in that time, but it still feels the same to me, as it still works the same from a user perspective (entries can be added via a web interface, email, file (that was true even 25 years ago) and the PUT method (added last year); the storage system hasn't changed either and is backward compatible such that the code in 2001 (when I first went public) could still work on the data today). And yes, it is still a CGI script. I saw no need to change that over the years.
Obsidian Publish, Micro.Blog, Ghost, BearBlog, HackMD, etc. are all great places to start, with less "baggage" associated with them. I know a lot of people write on Medium as well, but the account requirements that pop-up randomly are super annoying.
No point hosting a blog or anything of the sort, unnecessary effort in the beginning when you don't know if you'll continue.