comment on

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?

:-o

Just some ale induced wonderings on a late Thursday night

In reply to Touching it when it ain't broke by Marza

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks