I didn't get to sleep properly until about 4am so, in time honoured tradition, I wrote about it in the Journal, made some edits to code and CSS, and put the cricket on (the Ashes first test) – it looks like I missed the best bits from England's perspective.
2026/07/15#p1
2026/07/15#p1
Hello November. Where did you sneak up from? Aren't you a bit early? No? Oh, it feels like you are.
The monthly blog backup is done – the various files (images, video, audio) uploaded to the site. It's always a good feeling to know it's all tucked away should something bad happen.
I can't remember where, but I recently saw someone had a 'site changelog' on their blog. Here, the blog itself is its own changelog, I tend to post about any major changes – and some of the not so major ones. It got me thinking about how and whether this kind of thing needed to be tracked at all.
I recently added a 'meta' label but often forget to apply it, I think that says a lot. Things change here so frequently (I'm always tweaking the code, fixing glitches as they appear, and making other slight alterations) but most of those changes aren't visible and there is little value in commenting on most of them. Only those that impact the usage of the site really need to be mentioned in public.
Even so, some will only read posts via RSS and never visit the site at all – changes to look, feel and functionality will be irrelevant to them as long as the feed keeps getting generated.
I'm not really sure where I'm going with this. I will, however, continue to post about various changes for my own reference if nothing else. It's good to keep track of how things develop, even if only to remind myself of my thought processes at the time and what did or didn't (in my opinion) work.
