Bad Software At Work
I had a longer idea to turn in for today, but after an 11 hour work day, I’m passing on writing an essay for tonight. I’m going to turn in some yeoman’s work here and go play some Halo.
It’s not that I don’t care, but let’s face it the only loser reading this late Friday night is me. That said, I’m not going to write about nothing for a couple of hundred words, just this paragraph. (And the one before it.)
One of the things that really bothers me about enterprise software is just how terrible the interface can be. Whether it’s terribly out of date order software written in an ancient version of Java, or a swish new web server interface with no logical flow— enterprise software always seems to lack that spark that has driven the consumer revolution.
I can acknowledge that the main audience, Sysadmins, might be part of the problem. We’re people who simply don’t need software to be great. We’ll fight with it, hack it, and do whatever it takes to keep it running. Business users aren’t much better audiences. Most of the time they’d rather deal with bad software than deal with their IT departments. Things have changed in the last few years as consumer IT drove the enterprise through a revolution of modernization. However, there's a lot of bad software still lingering out there in various states of broken. There’s still a long way to go, and I’m not sure that it will ever get all the way there. The incentive is to push things out the door and iterate in the upgrade cycle, relying on support to keep things held together in the meantime.