Several times, I’ve mentioned one of the projects I’ve been working on this year: a website for the music team at my church so we are all singing off the same chord sheets. The basic site was hand-coded and ready early on in the year and I’ve been gradually adding refinements. For example, in April, I created a feature that let us save sets of songs so now I can look back and see which songs we’ve sung at each service, including who led them and what key they picked.
Since I started using AI supported development tools, it has become very easy to add further enhancements. Since each time I do this, it builds my skills in using those tools for my professional work, there have been several further developments. Tonight’s took less than half an hour, although I’ve been pondering the concept for a few days. When I started the system, I had a large collection of ChordPro files. I’d worked out how to get them to display on the website but quickly realised that it was easier to process them into a JSON-based format for storage. I’ve still got my ChordPro collection but now I’ve also got a JSON collection and the two aren’t perfectly in sync. If I discover something that needs changing, I’ll make the changes directly in the JSON. That’s been fine but I’ve now discovered another thing I want to do where it would be helpful to have a ChordPro version of the current JSON file.
I’ve now added that as a new feature, albeit one that isn’t yet part of the advertised interface and initial tests suggest it is working well. Mind you, metaphorically, what I’m doing is no less than sending the sausages back through the mincer!

