Originally posted by Ernest Friedman-Hill:
One thing that's very important in the process is having good tools. Hopefully you're already using an IDE with strong refactoring support built in? With such an IDE (and experience using it) a lot of very painful, tedious work can be eliminated.
At first, it could be impossible to write true unit tests, so write application tests. Write tests that document the way the whole application works, and then run them after doing a refactoring to ensure that it still works the same way.
Originally posted by Ken Blair:
For example, replacing all usages of a certain method with calls to a different method following a certain template.
Originally posted by Clifton Craig:
Maybe I'm just making a stink and I don't really know what I'm talking about.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton