What are the underlying reasons for this apprently unusual strategy? Firstly, there's the old adage 'the grass is greener on the other side' - maybe our system is getting long in the tooth, maybe we're having trouble with the supplier, maybe our company is being held back because we aren't using the latest technology.
It could be as simple as a personailty clash between an incoming IT manager and an existing computer system. The "I didn't select it so it can't be any good" syndrome. Or it could be bored support staff needing some new toys to play with.
Here are my golden rules that should apply when considering a change to a different computer system:
- If it's Open Source, change to Closed Source (but remember, it's important psychologically to have someone to blame if it goes wrong)
- If its Closed Source, change to Open Source (wow, we get the source as well?)
- If it's character-based, change to GUI (pretty colours, dials and knobs)
- If it's GUI, change to a Web-based system (more pretty colours and graphics)
- If it's Web-based, change back to character-driven (wow, it's so much faster)
As it usually takes a long time - often years - to finally change over from one system to another, a prudent rule is: always keep two systems running.
The most opportune time to think about changing your computer software is when you've finally powered-down its predecessor system for the last time; up until then you haven't had time to properly think about the future as you've been busy maintaining two systems.
What's the lesson for developers trying to sell their software? Always keep up with the latest fashions. And the lessons for developers with older systems? Add some pretty, bleeding-edge facilities. Put in some useless xml-rpc call, or add in one program written in "insert flavour of the month programming language here" or even better, invent your own. Even if it doesn't enhance the system, it'll still work wonders on your resume.
John Leach is Managing Director of Melbourne-based open source consultants Osware. You can reach John by e-mail at johnl@osware.net or on the Web at http://osware.net
6%
1%
