I use 2), but *try* to keep in mind the old adage "if it ain't broke
don't fix it".  When you mess with production code it becomes dev
server code again; mostly due to stoopid typos made inadvertently
during the re-dev process.  Very often I create more trouble for
myself and wish I had left the code alone... but despite that I think
the benefits of evolution overcome the growing pains.

When I do re-do code, I try to keep it as part of a general overhaul.
Say, a new release to add Feature X; While I'm at it I'll also run
thru the code and do whatever else I think it needs.

--
--Matt Robertson--
MSB Designs, Inc.
mysecretbase.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to