I’ve been using WordPress on my blog for so long, I don’t even really remember when I converted to using it from my homegrown system. My post archives suggest it happened some time in 2010, so that’s a long time to be on a platform I ultimately disliked. Heck, I hated the Gutenberg block writing system so much I followed a guide to disable it. And then I installed an actual plugin to disable it permanently.
Jen suckered me into volunteering to help her music boosters with their choir contest this weekend. This entailed waking up at 4:45AM so we could leave at 5:30AM to finish setup and get ready for the festivities to begin at 8:00AM. Woo? My job description was Sound Technician for the day, where I handled four Sony voice recorders; three for the judges and one to record the choir. Each choir used between eight and twelve minutes for two or three songs, but each time block was twenty to act as a buffer between groups.
There’s a lot of debate in application development circles over various sundries such as column naming schemes and framework implementation details. Well, I’d like to clear all that up.
See, there are more application frameworks than grains of sand on the entire planet Earth, and each one of them has a different philosophy and API for creating database objects. Rails, Django, Turbogears, Zope, Zoop, Drupal, Catalyst, Nitro, Nuke… holy fucking Christ, stop it already! Apparently each individual person who glanced at a programming book last week thinks that language is the epitome of cognitive design, yet is incapable of operating a search engine, so decides to shit out an application framework collecting his or her various insights and pet peeves into a pulsating monstrosity that inevitably and mysteriously gathers followers, like an insidious cult.