Maintenance

Way back in the day – and by that, I mean around 1998-2000 – I used to keep a personal page about the weirdo things we would field from people about their technical issues. This was originally set up on a GeoCities page. Remember that? At the time, it was groundbreaking: a place where you could build an online presence in a “city” where other sites similar to yours also lived. Eventually, I moved the content to its own domain.

The point of this history lesson is that at that time, HTML was language, and the page I maintained and updated weekly required me to go right in to the code and modify it to put in the things I needed to put in. It was a great experience: learning some things from the ground up, troubleshooting what didn’t work after you updated a page and finding that you left a termination code out, and deciding just which h codeĀ  you wanted to have for the title and headings to make them normal sized or large or gigantic and bold, and so on.

As time passed, of course people developed content management systems in perl and PHP and the world drifted over from doing things in HTML to doing things in other languages, first in raw files and then in applications people developed to make creating and maintaining sites much easier than they had been.

Fast forward to today. We’ve absorbed clients from other hosts over the years, and some of those sites are still anchored in HTML, built by those hosts and then not really updated code-wise, even if they had a maintenance contract with the user. When we inherited those folks, we also inherited the content modification requests. This is forcing me to take a very deep dive back into the brain and go retro on the editing the user wants to have done. I firmly believe that challenges like this keep those brain cells active, and according to “they”, this can only be a good thing.

And now back to that deep pool in the brain, swimming in HTML code.

Until next time, peeps: be well.