×

Uh-oh, it looks like your Internet Explorer is out of date.

For a better shopping experience, please upgrade now.

Working Effectively with Legacy Code (Robert C. Martin Series) / Edition 1
  • Alternative view 1 of Working Effectively with Legacy Code (Robert C. Martin Series) / Edition 1
  • Alternative view 2 of Working Effectively with Legacy Code (Robert C. Martin Series) / Edition 1
     

Working Effectively with Legacy Code (Robert C. Martin Series) / Edition 1

4.0 3
by Michael Feathers
 

See All Formats & Editions

ISBN-10: 0131177052

ISBN-13: 9780131177055

Pub. Date: 10/01/2004

Publisher: Prentice Hall

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

Overview

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 efforts.

In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control.

The topics covered include

  • Understanding the mechanics of software change: adding features, fixing bugs, improving design, optimizing performance
  • Getting legacy code into a test harness
  • Writing tests that protect you against introducing new problems
  • Techniques that can be used with any language or platform—with examples in Java, C++, C, and C#
  • Accurately identifying where code changes need to be made
  • Coping with legacy systems that aren't object-oriented
  • Handling applications that don't seem to have any structure

This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

Product Details

ISBN-13:
9780131177055
Publisher:
Prentice Hall
Publication date:
10/01/2004
Series:
Robert C. Martin Series
Edition description:
New Edition
Pages:
456
Sales rank:
165,355
Product dimensions:
7.00(w) x 9.25(h) x 0.92(d)

Table of Contents

Preface.

Introduction.

I. THE MECHANICS OF CHANGE.

1. Changing Software.

2. Working with Feedback.

3. Sensing and Separation.

4. The Seam Model.

5. Tools.

II. CHANGING SOFTWARE.

6. I Don’t Have Much Time and I Have To Change It.

7. It Takes Forever To Make a Change.

8. How Do I Add a Feature?

9. I Can’t Get This Class into a Test Harness.

10. I Can’t Run This Method into a Test Harness.

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

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

13. I Need To Make a Change but I Don’t Know What Tests To Write.

14. Dependencies on Libraries Are Killing Me.

15. My Application Is All API Calls.

16. I Don’t Understand the Code Well Enough To Change It.

17. My Application Has No Structure.

18. My Test Code Is in the Way.

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

20. This Class Is Too Big and I Don’t Want It to Get Any Bigger.

21. I’m Changing The Same Code All Over the Place.

22. I Need To Change a Monster Method and I Can’t Write Tests for It.

23. How Do I Know That I’m Not Breaking Anything?

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

III. DEPENDENCY BREAKING TECHNIQUES.

25. Dependency Breaking Techniques.

Appendix: Refactoring.

Glossary.

Customer Reviews

Average Review:

Post to your social network

     

Most Helpful Customer Reviews

See all customer reviews

Working Effectively with Legacy Code (Robert C. Martin Series) 4 out of 5 based on 0 ratings. 3 reviews.
Guest More than 1 year ago
Feathers confronts a depressingly familiar problem encountered by many programmers. How to maintain a system of legacy code? Where often there has been no rigorous attempt to test it. Even in a manual fashion. He shows ways to build a test harness to automatically test the code. Even if this does not perform an exhaustive test, it may still be far in advance of what you already have (nothing?) to validate the code. He writes assuming that you might never have met a disciplined testing approach. So unit testing is carefully explained and he builds from there. Simple, useful patterns like Decorator are described. The book is not meant as a comprehensive exposition of patterns. But hopefully, you can see the general idea of patterns and its utility. Large portions of the book are essentially about refactoring legacy code into these patterns, if possible. And also about testing your changes in a systematic way. If you do the former, you should also do the latter. The examples are mostly in C++ and Java. But that's neither here nor there, if you program in other languages like C# or C. The ideas from the examples carry over well.
Anonymous More than 1 year ago
Anonymous More than 1 year ago