I'm a big fan of continuous improvement. When you notice bad code while working on it (or perhaps even near it), make it better.
I don't see any purpose in taking out time to go back and beautify ugly code you haven't touched in six months (or more!) though. Wait until you need to work on it, then make it better. If you never work on it again, there was no need to make it better in the first place. Just my 2 <cfoutput>#smallest_denomination_of_currency_of_your_choice#</cfoutput>. Sam On 10/26/07, Phillip Senn <[EMAIL PROTECTED]> wrote: > > > > No matter what code I write it always embarrasses me a year or so > later. > > Oh wow! > What a great life-lesson. I've been pondering lately that 50% of coding > should be taking out the garbage. > > Maybe another 10% should be revisiting / refactoring every 6 months. > > But as I told a friend who was trying to justify a .5% tax increase: > "Hey!" I said. "I've only got a hundred of those things!" > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
