In developing my webdev skills I do have a bit of a tendency for rabbit-holing – exploring tunnels where I scent something that may be of interest. That can be a bit of a time thief if left unchecked but I do like to allow a bit of space in my schedule. After all, it is the same tendency that got me into web development in the first place, discovering how to write HTML, how to publish it on a server and then a whole array of further skills gleaned over the years. It has also been the source of some nuggets of understanding that have allowed me to do things that have increased my productivity, like when I discovered the Vim editor while watching a programming demo at a trade show, which I’m still using almost daily over 20 years later.
Today I’ve allowed myself a bit of time to explore something called HTMX. It is a lightweight JavaScript framework that makes it easy to replace a subsection of a web page or perform other operations without having to reload the whole thing. That isn’t a new idea but I found myself watching a five minute video which gave me the scent of something that could be a useful addition to my toolkit.
This evening, I’ve put a bit of time into watching another video or two, looking over the documentation and, with some help from Cursor (practising another newish set of skills), building a useful new feature for one of the websites I maintain as a development playground. Fellow members of my church worship team can now update the key of a song included in a set at will (previously that required me to have access to the database to update a set). Last week in the pre-service practise, a key was changed at short notice and it would have been useful. I’m not at the service tomorrow (preaching at St Theo’s again) but they are out in the park and I anticipate that the guitarist who is leading a couple of songs may want to adjust the keys for the outside setting, where voice projection requires more than getting close to a microphone.
Key changing isn’t entirely new to the application but the previous version didn’t work with the set view and got undone if you changed the key of another song on the page where it was available so this is definitely an enhancement and, although the codebase is continuing to bloat at them moment, the fact I’ve had to create a system to return the code representing a single song means I can tidy up all the places I show songs by ensuring they use the same approach.
So, within time boundaries, I’ll be continuing to go rabbit-holing from time to time.