It's been absolutely yonks since I've updated anything related to the blog, but finally here it is: the hot new oldness or more of the same. I've tried as much as possible to *not* hack the plugins I'm using with this version of the cms since that's a recipe for difficult upgrades and one of the reasons it took so long to do any kind of change. I'm also not that happy that I'm still using Wordpress, but their network effect is still going strong, especially with regards to plugins.
I haven't had a lot of time, or for that matter desire, to check the IE family of bad renderers, so I'm sure it's borked. I do that kind of thing for a living, so it behooves me sometimes to do it also in my spare time. I'm sure I'll get to it eventually.
Thusly, onwards.
# § Blog Great photograph by Noah Kalina
#
§ Blog, brooklyn, musician, NYC, photo, photographer
My boss' new blog that is an addendum to his upcoming O'Reilly book. # § Blog, Design, UI, Usability, Workplace
For some insane reason, I got the itch to try and update the blog with the recently released latest and greatest "software hooha-ery":http://wordpress.org/. After about two hours of back and forth between looking up the new api changes and updating my custom-built-with-php-and-cheezits site, it was obvious what a gigantic pain in the ass this process was going to be.
This was of course not the fault of the updated software (which handled the core upgrade quite well; Kudos to the Wordpress folks for that), but rather my lack of foresight. Instead of taking the time to make plugins as simple wrappers for all of the default template hacking and custom sql I use, I just stuck it in the default templates and left it at that. No fuss at at the time. I love writing elegant code as much as the next person (I do it for a living), but I'm also a pragmatist. This certainly isn't rocket science and it's just a blog, so I really didn't care too much about it.
That was two years ago. Of course now that I want to upgrade, I have to remember why I wrote a particular function in a particular spot, which makes the itch to not only upgrade the backend software, but to retire the hedgehog that much greater. I also used the backend to store data in unintended ways, which served my needs at the time, but is biting me now since I have hundreds of posts that look kind of funky with this new version.
So what should have initially been a 30 minute upgrade will most likely be a two weekend or more project that is entirely dependent on how much time, energy and interest I'll still have by the end of it. Welcome back to the upgrade cycle. I'm seriously considering going static and ascii for the whole thing (how's that for cutting off your nose to spite your face). #
§ Blog
Awesome English MP3 blog. # § Blog, England, Music, Uncategorized
After migrating my movable type database over several machines, many months and multiple mysql fink upgrades by simply copying the database file, I finally broke some binary link that kept the table indexes valid. Thusly, I've had to rebuild my entire mt installation from scratch using exported entries, backed up sql files and dozens of custom MT templates.
There are a couple of things I've learned from this tedious reconstruction incident, one of them so underwhelmingly illuminative, I shall dub it sotto's razor:
It is very difficult to build a modular system. However, it is an even greater pain in the ass to reconstruct from scratch said system through its modular parts.
Oh, and the other thing I've learned has to do with using a real hosting company and not keeping your site on your normal everyday use Powerbook.
# § Blog