Working Effectively with Legacy Code

Name: Working Effectively with Legacy Code
Price: 21.28 USD
Availability: InStock
ISBN: 9780131177055

ISBN-10: 0131177052

ISBN-13: 9780131177055

Edition: 2005

Authors: Michael Feathers

List price: $64.99

This item qualifies for FREE shipping.

30 day, 100% satisfaction guarantee!

Sell

Get cash fast!

Buy new: $45.99

Marketplace

5 new & used from $21.28

what's this?

Rush Rewards U
Members Receive:

You have reached 400 XP and carrot coins. That is the daily max!

This book provides programmers with the ability to cost effectively handlecommon legacy code problems without having to go through the hugelyexpensive task of rewriting all existing code. It describes a series of practicalstrategies that developers can employ to bring their existing softwareapplications under control. The author provides useful guidance about how touse these strategies when refactoring or making functional changes to codebases. One of the book's key points is that it teaches developers to write teststhat can be used to make sure they are not unintentionally changing theapplication as they optimize it. Examples are provided in Java, C++, and Csharp,and the book assumes that…

Book details

List price: $64.99
Copyright year: 2005
Publisher: Pearson Education
Publication date: 9/22/2004
Binding: Paperback
Pages: 464
Size: 7.00" wide x 9.25" long x 1.20" tall
Weight: 1.914



Preface


Introduction



The Mechanics Of Change



Changing Software



Working with Feedback



Sensing and Separation



The Seam Model



Tools



Changing Software



I Don't Have Much Time and I Have To Change It



It Takes Forever To Make a Change



How Do I Add a Feature?



I Can't Get This Class into a Test Harness



I Can't Run This Method into a Test Harness



I Need to Make a Change. What Methods Should I Test?



I Need to Make Many Changes In One Area Do I Have To Break



I Need To Make a Change but I Don't Know What Tests To Write



Dependencies on Libraries Are Killing Me



My Application Is All API Calls



I Don't Understand the Code Well Enough To Change It



My Application Has No Structure



My Test Code Is in the Way



My Project Is Not Object-Oriented. How Do I Make Safe Changes?



This Class Is Too Big and I Don't Want It to Get Any Bigger



I'm Changing The Same Code All Over the Place



I Need To Change a Monster Method and I Can't Write Tests for It



How Do I Know That I'm Not Breaking Anything?



We Feel Overwhelmed. It Isn't Going To Get Any Better



Dependency Breaking Techniques



Dependency Breaking Techniques


Appendix: Refactoring


Glossary