During the discusion of So you know Perl; but do you know programming?, Abigail-II remarked the old saying "Don't touch it if it ain't broke"
After pondering this statement. I tend to think that there is a good time to "fix" something.
Usually, it can be argued that it is a waste of time since we are always doing something on the job. However, my question is now this:
Why not fix things if you are going to have to make major mods on the script anyway? The perfect time would be before the new feature is added. You already know what the script is doing so if you do something wrong, you can respond quickly. A "cleaner" script might make the additions/mods faster
Then, there is the fact you also add time to the job.
All in all, I would think changing it when you are making mods are justified.
Hmmmm can I be a perfectionist?
:-oJust some ale induced wonderings on a late Thursday night
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Touching it when it ain't broke
by oakbox (Chaplain) on Aug 09, 2002 at 07:10 UTC | |
by Marza (Vicar) on Aug 09, 2002 at 23:33 UTC | |
Re: Touching it when it ain't broke
by Ovid (Cardinal) on Aug 09, 2002 at 18:15 UTC | |
by pdcawley (Hermit) on Aug 11, 2002 at 22:39 UTC | |
Re: Touching it when it ain't broke
by Zaxo (Archbishop) on Aug 09, 2002 at 10:59 UTC | |
Re: Touching it when it ain't broke
by hsmyers (Canon) on Aug 09, 2002 at 13:37 UTC |