Working Effectively with Legacy Code (häftad)
Häftad (Paperback)
Antal sidor
1 Ed. of 2005
235 x 175 x 30 mm
840 g
Antal komponenter
Working Effectively with Legacy Code (häftad)

Working Effectively with Legacy Code


(3 röster)  |  Läs 1 recension
Häftad,  Engelska, 2004-10-01
  • Skickas från oss inom 5-8 vardagar.
  • Fri frakt över 249 kr för privatkunder i Sverige.
Working Effectively with Legacy Code Kan levereras innan julafton
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 platformwith 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.

Copyright Pearson Education. All rights reserved.
Visa hela texten

Passar bra ihop

  1. Working Effectively with Legacy Code
  2. +
  3. Tidy First?

De som köpt den här boken har ofta också köpt Tidy First? av Kent Beck (häftad).

Köp båda 2 för 959 kr


Det finns 1 recension av Working Effectively with Legacy Code. Har du också läst boken? Om du har köpt den på vill vi gärna höra vad du tyckte om den! Sätt ditt betyg »
  1. Måsteläsning för utvecklare
    Per Lundholm, 5 september 2019

    Alla får sitta med gammal kod som plågas av hög teknisk skuld. Det är inte alltid så men ofta. Den här boken innehåller mycket bra mentala verktyg för att angripa monoliter. Stora som små.

Visa alla 1 recensioner

Övrig information

MICHAEL C. FEATHERS works for Object Mentor, Inc., one of the world's top providers of mentoring, skill development, knowledge transfer, and leadership services in software development. He currently provides worldwide training and mentoring in Test-Driven Development (TDD), Refactoring, OO Design, Java, C#, C++, and Extreme Programming (XP). Michael is the original author of CppUnit, a C++ port of the JUnit testing framework, and FitCpp, a C++ port of the FIT integrated-testing framework. A member of ACM and IEEE, he has chaired CodeFest at three OOPSLA conferences. (c) Copyright Pearson Education. All rights reserved.





  1. Changing Software.

  2. Working with Feedback.

  3. Sensing and Separation.

  4. The Seam Model.

  5. Tools.


  6. I Dont 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 Cant Get This Class into a Test Harness.

10. I Cant 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 Dont Know What Tests To Write.

14. Dependencies on Libraries Are Killing Me.

15. My Application Is All API Calls.

16. I Dont 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 Dont Want It to Get Any Bigger.

21. Im Changing The Same Code All Over the Place.

22. I Need To Change a Monster Method and I Cant Write Tests for It.

23. How Do I Know That Im Not Breaking Anything?

24. We Feel Overwhelmed. It Isnt Going To Get Any Better.


25. Dependency Breaking Techniques.

Appendix: Refactoring.