Working Effectively with Legacy Code (Robert C. Martin Series)
This is the eBook version of the printed book. If the print book includes a CD-ROM, this content is not included within the eBook version.\ Get more out of your legacy systems: more performance, functionality, reliability, and manageability\ Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development...
Search in google:
Feathers (Object Mentor) presents his approach to making sense out of legacy code, and describes techniques for getting it under test, refactoring it, and adding features. He discusses instantiating a class in a test harness, adding behavior to existing classes, reasoning forward about effects, controlling the size of classes, and several dependency-breaking techniques. The short code examples are written in Java, C++, and C. Annotation ©2004 Book News, Inc., Portland, OR
Foreword1Changing software32Working with feedback93Sensing and separation214The seam model295Tools456I don't have much time and I have to change it577It takes forever to make a change778How do I add a feature?879I can't get this class into a test harness10510I can't run this method into a test harness13711I need to make a change : what methods should I test?15112I need to make many changes in one area17313I need to make a change, but I don't know what tests to write18514Dependencies on libraries are killing me19715My application is all API calls19916I don't understand the code well enough to change it20917My application has no structure21518My test code is in the way22719My project is not object-oriented : how do I make safe changes?23120This class is too big and I don't want it to get any bigger24521I'm changing the same code all over the place26922I need to change a monster method and I can't write tests for it28923How do I know that I'm not breaking anything?30924We feel overwhelmed : it isn't going to get any better31925Dependency-breaking techniques325AppRefactoring415
