| OverviewGet 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. © Copyright Pearson Education. All rights reserved. Editorial ReviewsProduct DescriptionThis 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 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. |
Other Readers Also Read | Top Sellers in This Category | Browse Similar Topics | | | Top Level Categories:Sub-Categories: | | | | |
Reader Reviews From Amazon (Ranked by 'Helpfulness') Average Customer Rating: based on 28 reviews. Essential reading to sharpen your tools, 2009-05-21 Reviewer rating: This is a must-read for software engineers. It clarifies some powerful techniques for bridging the gap between legacy (test-less and/or untestable) code and fresh, testable code. And BTW legacy doesn't necessarily mean somebody else's code, it could be code you wrote last week. | Great book, 2009-03-16 Reviewer rating: Excellent book helping you to handle legacy systems. Gave me a lot of ideas on how to go on with the system I am working on. Only complaint I have is that it does not discuss legacy systems where you might need to a relational model already containing production data. | Foundational Knowledge Most Lack for the Average Developer, 2009-02-18 Reviewer rating: Quite simply you cannot afford to be lacking this knowledge as it is simply standard in software organizations where success is not something taken lightly. | best book on working with other people's code, 2008-12-24 Reviewer rating: Short and to the point. Filled with great techniques for handling legacy monsters. Much more practical than Martin Fowler's Refactoring book. | Great book!, 2008-12-20 Reviewer rating: This is the canonical book for working with legacy code (and you can even learn some if you're not working with legacy code). I use the things I learned from it daily! |
Some information above was provided using data from Amazon.com. View at Amazon > |
| |
|
|
