Feb 22

A few years back, I bought an Apple Time Capsule.  I had just purchased a new iMac to replace my Power Macintosh G5.  The G5 had two internal drives, allowing me to use Time Machine (Apple’s automatic incremental backup/snapshot system) on the second drive.  As the iMac has no provision for a second internal drive, my choices were to attach an external drive, or go for the Time Capsule.  I bought the Time Capsule, thinking it would be more useful: it could also back up a few other Macs in the house.

I just bought a newer iMac, and I bought a FireWire external disk for it and migrated my backups.  It’s time to bury the Time Capsule.

Continue reading »

Apr 18

I love JIRA, I really do, so long as I never have to do any administration to it.

I’ve got a JIRA instance set up as a household to-do system.  Today, I tried installing JIRA 4.1 as a test instance, upgrading from version 4.0.  It turns out I won’t be making that upgrade for real any time soon, as 4.1 breaks many of the plugins I need for my JIRA workflow.  If I upgraded, I’d cripple my setup beyond usability.

Unfortunately, Atlassian has chosen to leave many obvious and necessary workflow actions out of JIRA, instead relying upon third-party plugins to provide them.  This wouldn’t be a problem if Atlassian didn’t change their plugin API more often than Tiger Woods picks up new sexual partners.

Continue reading »

Tagged with:
Apr 12

[Edit: added one of the biggest examples i forgot while drafting this: the JIRA dashboard.]

I’m not particularly fond of Linux. I’ve used it, and it’s good for many things, but as a professional system administrator I prefer Solaris, or FreeBSD, or even Mac OS X (as a UNIX). Why? A great many of the Linux enthusiasts I’ve had to deal with have suffered from what I call Shiny Object Development Syndrome (SODS).

SODS is characterized by a tendency to concentrate on developing new features that are pleasing and attractive to the developer, with a complete disregard to the usefulness, usability, or basic function of the product itself. It is particularly prevalent amongst open-source developers, particularly those who work on obscure Linux distributions.

Developers who suffer from SODS are often heard replying to legitimate user complaints with some variation on “you can fix it yourself if it’s important to you, the source code is available.”

Sometimes SODS infects an entire organization. When this happens to a company with paying clients, symptoms include: refusal to fix longstanding bugs; failure to supply updates to widely-deployed, stable versions when longstanding bugs are finally addressed; issuing updates that break existing functionality such as extensions, plug-ins, or settings.

Terminal company-wide SODS often reveals itself as intractable bugs pile up because the new shiny features beloved of the developers and the marketing department depend upon so much spaghetti code that it becomes impossible to fix all the problems without starting over from scratch. By this stage, the company usually begins to hemorrhage users as the cost of migrating to another platform becomes cheaper than dealing with the SODS-ridden status quo.

A good example of a company full of SODS is Atlassian.

Continue reading »

Tagged with:
Jan 11

This blog entry was originally published on November 9, 2002.

While The Art of Turboing is all about how to complain with extreme prejudice, sometimes the same technique is useful when you have compliments or constructive criticism. Sometimes, it’s even profitable.

Read on to find out what happened when I shared some thoughts with the CEO of BJ’s Wholesale Club. Continue reading »

preload preload preload

Bad Behavior has blocked 88 access attempts in the last 7 days.