Moving my code-blogging efforts here

As I'm between jobs (again), I decided to use some of my free time to start collecting and packaging various personal projects, and to write about them. Initially, I tried posting these on LinkedIn, but their article system apparentlyhas issues with preserving things like images and code-snippets, at least when articles are published on a scheduled basis. As a result, I'm moving those efforts here instead — I've generally had good luck in the past with Blogger, though it's not as sophisticated as I might like.

The stories behind many of these packages is vaguely similar, generally following this pattern:

• Some (usually minor) issue surfaces at work;
• The team I'm on comes up with some quick solution, typically a pretty good one, but maybe not optimal or elegant;
• At some subconscious level, the problem nags at me, and I dream up some solution;
• I write the code to implement a better solution (even if better is just a matter of my opinion).

Since many of these issues and solutions have come up across several projects, or even several jobs, I decided to collect them into my own personal toolkit, initially. After being laid off at the beginning of 2025, I decided that I might as well formally package them up: even if I'm the only person who uses any of them, at least I could simply search under my common package prefix on PyPI, or in my public Bitbucket project for what I need. If my activities happened to benefit anyone else, so much the better, and maybe having some published packages out there would also serve as some sort of resumé boost during my ongoing job-hunt. I've had my blogging efforts be a significant differentiator in the past.

On a longer-term basis, I have some thoughts about several larger scoped projects that many of these package projects could be useful for. One in particular that I'd like to pursue is a website management/digital CMS/blogging platform of my own design, written to run using cloud-resident serverless resources and functionality. While I'm not displeased with Blogger as an outlet for this content, it's not what I'd really like, either. Hopefully I won't be engaged in the job-hunt for long enough to actually see that come to fruition, but if I do, I do.

My current plan is to publish an article twice a week, for as long as I have code that I can spare the time to work on, starting with re-publishing the articles that I originally wrote on LinkedIn.