Derek K. Miller - Penmachine words music comment - Vancouver, Canada

Today I had a meeting with the trial nurse for my upcoming resumed chemo treatments next month, followed by a series of blood tests, an appointment with my oncologist and the nurse again, then a CT scan. In between, I had some time to kill, so I had lunch at White Spot, then took time to walk around the Fairview neighbourhood and experiment some more with high dynamic range (HDR) photography.

Here are the results:

For each photo, I set my Nikon D50 camera to take three bracketed exposures: one at the default exposure the camera estimates, one two stops darker, and one two stops lighter. Then I used Photomatix Pro on my Mac to assemble them into HDR images, then tone-map them into the pictures you see. It's fun.

Labels: art, cancer, chemotherapy, hdr, photography, software, vancouver

I used to teach courses about Microsoft Word. Stuff like this (via John Gruber) is what made me stop.

Labels: apple, macosx, microsoft, publicspeaking, software

I've used NetNewsWire as my RSS reader on the Mac for years. It's the best program of its kind, in my opinion. And now it no longer costs money. I sat for lunch with developer Brent Simmons and his wife Sheila a few years ago, and he is not only a smart programmer, but a nice guy.

If you read a lot of websites and blogs and would like to get the latest without constantly hopping from site to site, RSS is the way to go, and NetNewsWire is the way to get it if you have a Mac. Go download it.

Labels: geekery, macosx, rss, software, web

This site runs on Blogger, as it has for more than seven years, but if I were starting over again today I'd probably use WordPress. That's what I recommend to my friends and relatives, so that other sites I work with, such as Simon's, my wife's podcast (as well as her personal blog), and Inside Home Recording all use it.

If you use the free WordPress.com hosting service, all maintenance and upgrades are handled for you by the fine folks who run it. But if, like me, you're reasonably geeky and need the extra customization available by running WordPress on your own server, the main hassle has been that, when a new version of WordPress comes out, upgrading the software involves:

1. Backing up your installation.
2. Downloading the latest version of WordPress.
3. Deactivating all the WordPress plugins on your sever.
4. Putting your website into Maintenance Mode (basically, activating a page that says, "Hold on, we'll be right back" to your web visitors).
5. Uploading a whole ton of updated files to your server, usually in several stages so you don't accidentally overwrite any of your own customizations, plugins, or themes.
6. Running an upgrade script to update the database.
7. Taking the site out of Maintenance Mode.
8. Checking to make sure nothing's broken.

I've gotten reasonably good at that, but it's still time consuming, especially for multiple sites. Today, while surfing around feeling gross from chemo side effects, I read about the Automatic Upgrade Plugin (via Scott Beale on Twitter). It does all of that stuff with only a few clicks.

I tried it on two websites without a hitch, even using the Automated Mode that avoids the multi-screen, "Here's the next step, CLICK HERE if you're sure you want to proceed" process—with hardly a hitch.

Then, confident, I proceeded to the third site, Inside Home Recording, again in Automated Mode, got almost all the way through, and encountered the dreaded "500 Internal Server Error" page. I tried rolling back to my previous installation of WordPress manually. No dice. I noticed even the IHR forums (which use different software) were dead, which was mysterious and a bit freaky. And when I tried putting a generic "Sorry I broke the site" HTML page at index.php or index.html at the root of the site, it still didn't work. Yikes! I'd blown up the whole website!

I had a hunch, and took a peek at the invisible .htaccess file. That's a plain old text file sitting on the IHR web server (which I think is in Texas). The ubiquitous Apache web server software it's running uses .htaccess as a list to answer the question, "What do I do with stuff on this machine when I sent it out to the Web?" It seems that either WordPress or the Automatic Upgrade plugin had added some extraneous stuff to the end of that file. I deleted the extra text and, bingo, IHR was back up.

Having rolled back to the older version of WordPress, I made sure I had proper backups again (I remind you, back up, back up, back up your stuff), then tried the Automatic Upgrade plugin once more, but this time in Manual Mode (i.e. confirmed each step). No problems on this second attempt, and IHR is spiffed up with the latest software release.

Elapsed time from upgrade to blow up to fix up? Less than ten minutes. Sometimes I'm glad I have some web-fu when I need it.

Labels: backup, blog, family, friends, geekery, insidehomerecording, lipglossandlaptops, podcast, software, web

Last night was the Christmas party for Navarik, the company I've worked for since 2003, and for which I had the occasional contract in the three years before that. Several of my college colleagues founded it in 2000—a web software company started just as the web software bubble collapsed. It's about the same age as my younger daughter, or this blog.

Early on Navarik was the leanest of self-funded startup companies, with a tiny office where people were nearly stepping over each other and everyone could go for lunch around one table. Last night I looked around and realized that it is no longer a startup at all. The many employees who have been there nearly from the beginning are now seasoned veterans (with far more experience than, say, the folks who run Facebook; Navarik itself is several years older than Flickr and WordPress). We've brought in more seasoned veterans over the years to help run the place.

Pointedly, Navarik has hired more new people since I went on medical leave in February (and thus with whom I've never worked directly) than formed the entire company when I started. Some of them I'd never met until last night. Back in 2003 only a couple of us in the office had children; in the past two years there has been a substantial baby boom, enough that we're having another Christmas party next week, just for all the kids.

The business we do is not flashy or high-profile, though it requires considerable skill and intellectual effort. We help some very big companies move important, money-making information around. Our website needs updating to reflect what that means in 2007 (that's one thing that's not getting done while I'm away), but it is fundamentally the same vision that Bill, the company's founder, had while working in the marine bulk shipping industry in the late 1990s.

I'm itching to get well again and return to helping make that vision real. I joined Navarik more than four years ago not simply because my friends started it. Rather, I saw a company built on new technologies and ideas, created for the Internet, that could show important worldwide industries how to do better than the clumsier old world of traditional information technology.

That's not Web 2.0 hype, but a real business. And a strong one, I think.

Labels: cancer, holiday, navarik, software, web

Microsoft has been diligent in releasing updates to its Office 2004 suite for Mac, largely to address security vulnerabilities. That's good. But their updater software sucks. Here's why:

The latest update is version 11.3.9. It turns out that I hadn't updated since 11.3.4 or thereabouts. Now, you'd think that the 11.3.9 update would update any version of Office to the latest version. Nope, here's what I had to install today:

If you look at those screenshots above, you'll notice that only one update appears in Microsoft's AutoUpdate software at a time. That's right, I had to run the updater, apply the version 11.3.5 patch, quit that, run the updater, apply the 11.3.6 patch, quit that... and so on.

I fear to think how long it would take if I had to reinstall from my original-release Office 2004 (11.0.0, I guess) disc. I suppose I should be glad I didn't have to reboot each time!

UPDATE: I forgot to link to my previous rant from last year about the even worse procedure I went through with Adobe Reader.

Labels: design, macosx, microsoft, software

I like what the Mozilla Foundation developers are doing with the user interface for the upcoming Firefox version 3 web browser: matching the interface elements to the operating system:

While Firefox looks good now...

...sharing a general appearance with other applications in Windows or the Mac OS will make it a better experience, and I think it's a good investment of developer time.

Labels: apple, design, firefox, macosx, microsoft, software, web, windows, windowsvista, windowsxp