A return to blogging

Periodically, I am reminded of lessons that I have learned in my past…

In particular, and most recently, I was reminded that sometimes building “workarounds” for perceived issues in software can, in fact, be a fairly enjoyable experience. However, when doing such, it is important to ensure that the solution is implemented in such a way that it has little impact on the core system. Otherwise, the solution will (likely) result in more issues in the future.

Case in point…this blog leverages the WordPress software. When I first installed the software, the comments system (powered by Disqus), and the theme…I experienced into an issue in the way in which certain information was presented. In an effort to make it meet my needs, I did a combination of theme tweaking (involving some interesting php parsing) and some database tweaks.

The first, expected and encouraged.
The latter, a fairly bad idea.

At the time, I had some content-driven categorization ideas and felt that the appropriate methodology for enabling such a workflow would be to change some database fields. Unfortunately, this resulted in an inability to perform any automatic upgrades to the core software.

Short story made long…

My monkeying resulted in an extraordinarily lengthy process whenever an upgrade was necessary. And, to the compliment of the WordPress community, upgrades are frequently available. At this point, the changes that were necessary are now solely implemented at the skin/plugin layer and no longer directly in the database.

Ultimately, my changes resulted in an inability to blog due to a partially upgraded state. I have exported all data and re-imported. Expect my level of pontification and comment on trends to return immediately.

Thanks for your patience during this time of “outage”. What can I say, the DBA in my past is still kicking about somewhere…

What’s your perspective? Agree? Disagree? Anything to add? Critiques? The comment form is below…

November 22, 2009

Leave a Reply

Your email address will not be published. Required fields are marked *