in reply to Touching it when it ain't broke

So I'm in a bit of a quandary has a discussion about updating old scripts in a production environment and how to deal with some of the social issues around it. One thing that I got out of the conversation is that there are three basic criteria to look at when contemplating a rewrite:
  1. Do you need to rewrite the script to add functionality now or in the future? A rewrite to make it easier to update will save you time in the future.
  2. Is the script a security hazard? Is it broken in some fundamental way that compromises your security?
  3. Do you require a boost in efficiency to handle higher traffic loads?
It looks like you are in situation 1. You need to look at your current update and how likely is it that future updates will be needed?


Replies are listed 'Best First'.
Re: Re: Touching it when it ain't broke
by Marza (Vicar) on Aug 09, 2002 at 23:33 UTC

    Thanks! Well after hunting and killing a small keg of ale, the super search function gets really hard to use! ;P

    You are correct in that my situation is number 1. The script in question has many future "updates" planned by my boss. So a re-write does make the planned changes easier. Especially now that I am smarter then when I first saw this script. ;)

    Thanks for the link! ++