I finally got to working through some of the issues with the song project. I created a git repository and pushed to a public GitHub repo.

Obviously, this is the beginning of the thing still, so there are some obvious things missing. At least I feel like I have an overall structure for the code now that I can fill out, and have a mechanism to track version history, which is a plus (and feels kind of good). This is the first time I’m doing anything to this extent (anything like an end-to-end project), so there are a lot of things I’m having to work through and learn as I go.

Next on the list, after I get the script to do what I want it to, will be setting up the Google Cloud Function and scheduling it, which I’m pretty sure is possible based on what I remember reading about them. Given the hang-ups that I’ve faced along the way, this feels pretty good. One surprising thing about this experience is just how fluid it’s been — in the process of working through a problem, I often end up with a completely different product from where I started, so who knows whether I’ll actually end up using Google Cloud Functions? Now I’ve started to wonder about how GitHub Actions may play with those and just how to integrate them, if that’s even an option. I suppose that’ll become clear as I continue to trudge along.

Another thing about this has been the effort in chronicling the process. As I go along, I’ve been trying to write up a blog post about how it’s going, how I’m feeling about it, and where I see it headed, and that, in and of itself, has been a whole learning process that has me thinking about how to optimize a totally separate thing. It’s not just coding and orchestrating and designing now; it’s also thinking about how to put thoughts to words, how to structure my writing, how the website should be laid out and organized, and how to increase traffic to it. Those things are secondary for now, but they are still on my mind, and that’s a wholly unexpected part of this process.