Well, maybe I spoke too soon about Drupal. Why? Well… it’s 2010 guys, stop with the ID links. I know there’s a plugin that overcomes this shortcoming, but all the internal links, including edits, redirects, and so on, won’t use the aliases you define. No, foo.bar.com/node/123423 is not a valid url. It requires approximately ten minutes to add a table column for a ‘slug’ to look up the appropriate entry, but Drupal refuses to compromise.
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!
