>>>>Last night I started reading a book called "Refactoring" by Martin Fowler. It discusses rearchitecting current applications. One of his statements is that "If it ain't broke, don't fix it" spells death for old applications.
>>>
>>>Excellent book, just wish we could use some of the refactoring tools and testing software he uses for his Java code.
>>
>>
>>I'm just getting into it, but it came highly recommended to me about a year ago. Steve Sawyer has a DevCon session based on this book.
>
>I have heard Steve Sawyer speak on refactoring. I recommend to everyone to attend his session. As for "if it ain't broke don't fix it", I like to think "if it ain't broke your not trying hard enough".

I never saw the wisdom in re-writing code that is doing what it was meant to do, without problems or errors. We have COBOL code written in the late 60's that is still being used unchanged, except for the Y2K fixes. One of the problems with "upgrading" is the need to keep the old system running while the new system is being developed and test. This often requires a data structure compatibility, eliminating any advantages that a newer DB or language might bring. There is a HUGE inertial resistance to change.
Besides, the legislature is always thinking up new things for me to do. I don't need to worry about rewriting a program that isn't causing problems and everyone is happy with.
JLK