 |
Refactoring: Improving the Design of Existing Code
Customer Reviews: 10 Average Customer Rating:  Write a Review and tell the world about this title! People who purchase this book frequently purchase: - Design Patterns: Elements of Reusable Object-Oriented Software; Erich Gamma, et al, $46.50, 22% Off!
- Refactoring to Patterns; Joshua Kerievsky, $46.50, 22% Off!
- Patterns of Enterprise Application Architecture; Martin Fowler, $50.50, 22% Off!
- Code Complete, 2nd Edition; Steve McConnell, $31.50, 37% Off!
Books on similar topics, in best-seller order:Books from the same publisher, in best-seller order:
As the application of object technology--particularly the Java programming language--has become commonplace, a new problem has emerged to confront the software development community. Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, "non-optimal" applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as "refactoring," these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use. . .until now. In Refactoring: Improving the Design of Existing Code, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process. With proper training a skilled system designer can take a bad design and rework it into well-designed, robust code. In this book, Martin Fowler shows you where opportunities for refactoring typically can be found, and how to go about reworking a bad design into a good one. Each refactoring step is simple--seemingly too simple to be worth doing. Refactoring may involve moving a field from one class to another, or pulling some code out of a method to turn it into its own method, or even pushing some code up or down a hierarchy. While these individual steps may seem elementary, the cumulative effect of such small changes can radically improve the design. Refactoring is a proven way to prevent software decay. In addition to discussing the various techniques of refactoring, the author provides a detailed catalog of more than seventy proven refactorings with helpful pointers that teach you when to apply them; step-by-step instructions for applying each refactoring; and an example illustrating how the refactoring works. The illustrative examples are written in Java, but the ideas are applicable to any object-oriented programming language.
Author Bio
Martin Fowler is the Chief Scientist of ThoughtWorks, an enterprise-application development and delivery company. He's been applying object-oriented techniques to enterprise software development for over a decade. He is notorious for his work on patterns, the UML, refactoring, and agile methods. Martin lives in Melrose, Massachusetts, with his wife, Cindy, and a very strange cat. Kent Beck, one of the software industry's most creative and acclaimed leaders, passionately employs patterns, extreme programming, and test-driven development. Currently affiliated with the Three Rivers Institute, he has been an author of many Addison-Wesley titles. John Brant and Don Roberts are the authors of the Refactoring Browser for Smalltalk. They are also consultants who have studied both the practical and theoretical aspects of refactoring for six years. William Opdyke's doctoral research on refactoring object-oriented frameworks at the University of Illinois led to the first major publication on this topic. He is currently a Distinguished Member of Technical Staff at Lucent Technologies/Bell Laboratories. John Brant and Don Roberts are the authors of the Refactoring Browser for Smalltalk. They are also consultants who have studied both the practical and theoretical aspects of refactoring for six years.
Table of Contents
1. Refactoring, a First Example.
The Starting Point.
The First Step in Refactoring.
Decomposing and Redistributing the Statement Method.
Replacing the Conditional Logic on Price Code with Polymorphism.
Final Thoughts.
2. Principles in Refactoring.
Defining Refactoring.
Why Should You Refactor?
When Should You Refactor?
What Do I Tell My Manager?
Problems with Refactoring.
Refactoring and Design.
Refactoring and Performance.
Where Did Refactoring Come From?
3. Bad Smells in Code.
Duplicated Code.
Long Method.
Large Class.
Long Parameter List.
Divergent Change.
Shotgun Surgery.
Feature Envy.
Data Clumps.
Primitive Obsession.
Switch Statements.
Parallel Inheritance Hierarchies.
Lazy Class.
Speculative Generality.
Temporary Field.
Message Chains.
Middle Man.
Inappropriate Intimacy.
Alternative Classes with Different Interfaces.
Incomplete Library Class.
Data Class.
Refused Bequest.
Comments.
4. Building Tests.
The Value of Self-testing Code.
The JUnit Testing Framework.
Adding More Tests.
5. Toward a Catalog of Refactorings.
Format of the Refactorings.
Finding References.
How Mature Are These Refactorings?
6. Composing Methods.
Extract Method.
Inline Method.
Inline Temp.
Replace Temp with Query.
Introduce Explaining Variable.
Split Temporary Variable.
Remove Assignments to Parameters.
Replace Method with Method Object.
Substitute Algorithm.
7. Moving Features Between Objects.
Move Method.
Move Field.
Extract Class.
Inline Class.
Hide Delegate.
Remove Middle Man.
Introduce Foreign Method.
Introduce Local Extension.
8. Organizing Data.
Self Encapsulate Field.
Replace Data Value with Object.
Change Value to Reference.
Change Reference to Value.
Replace Array with Object.
Duplicate Observed Data.
Change Unidirectional Association to Bidirectional.
Change Bidirectional Association to Unidirectional.
Replace Magic Number with Symbolic Constant.
Encapsulate Field.
Encapsulate Collection.
Replace Record with Data Class.
Replace Type Code with Class.
Replace Type Code with Subclasses.
Replace Type Code with State/Strategy.
Replace Subclass with Fields.
9. Simplifying Conditional Expressions.
Decompose Conditional.
Consolidate Conditional Expression.
Consolidate Duplicate Conditional Fragments.
Remove Control Flag.
Replace Nested Conditional with Guard Clauses.
Replace Conditional with Polymorphism.
Introduce Null Object.
Introduce Assertion.
10. Making Method Calls Simpler.
Rename Method.
Add Parameter.
Remove Parameter.
Separate Query from Modifier.
Parameterize Method.
Replace Parameter with Explicit Methods.
Preserve Whole Object.
Replace Parameter with Method.
Introduce Parameter Object.
Remove Setting Method.
Hide Method.
Replace Constructor with Factory Method.
Encapsulate Downcast.
Replace Error Code with Exception.
Replace Exception with Test.
11. Dealing with Generalization.
Pull Up Field.
Pull Up Method.
Pull Up Constructor Body.
Push Down Method.
Push Down Field.
Extract Subclass.
Extract Superclass.
Extract Interface.
Collapse Hierarchy.
Form Template Method.
Replace Inheritance with Delegation.
Replace Delegation with Inheritance.
12. Big Refactorings.
Tease Apart Inheritance.
Convert Procedural Design to Objects.
Separate Domain from Presentation.
Extract Hierarchy.
13. Refactoring, Reuse, and Reality.
A Reality Check.
Why Are Developers Reluctant to Refactor Their Programs?
A Reality Check (Revisited).
Resources and References for Refactoring.
Implications Regarding Software Reuse and Technology Transfer.
A Final Note.
References.
14. Refactoring Tools.
Refactoring with a Tool.
Technical Criteria for a Refactoring Tool.
Practical Criteria for a Refactoring Tool.
Wrap Up.
15. Putting It All Together.
References.
List of Soundbites.
List of Refactorings.
Index.
Customer Reviews
Customer Reviews: 10 Average Customer Rating: Nov 26, 2005
One of my all-time favorites!
This incredible book not only introduces the concepts and techniques of refactoring in way anyone can understand and implement, Martin Fowler's philosophical approach is amazingly refreshing.
I quote: "Now I'm a pretty lazy person, and am prepared to work quite hard in order to avoid work."
In addition to refactoring, I've learned more about testing from this one book than I have from any testing-specific title.
A must read!
Feb 3, 2004
Read it, Learn it, Use it.
This is one of those books that will always sit on my desk. There aren't that many of those. It is a perfect complement to Design Patterns and Code Complete.
Jan 25, 2004 Steve Revilak from Boston, MA
Essential Reading
Every once in a while you find a book that changes the way you think about programming. Martin Fowler's "Refactoring: Improving the Design of Existing Code" is one such book.
Often, one needs to modify or revise existing programs. This book presents a number of recipies for doing so; all with examples, and all in a step-by-step fashion. Not only are these ideas worthwhile when refactoring, they also serve as a set of guidelines for writing cleaner, simpler, and more maintainable code in general.
Jan 6, 2004 Anderson Ito from S. Paulo, Brazil
A must-have book!!
It is a very very interesting book!! A must-have if you are a serious developer. The techniques described must be part of a professional software engineer. This is an awesome title.
Dec 7, 2003 John Mors from Northern Virginia
How to improve your coding in one easy lesson
I have been programming since the era of punch cards, and have always been concerned with programming style. About 2 years ago I became interested in the process of coding and how code evolves as we add complexity ( XP ). This book formalizes a lot of what I had to learn the hard way. It has not only improved the clarity of my code, but also drastically improved my speed and accuracy. It has given me the ability to mentally picture multi-object systems and how I can evolve them into better code. I feel that after years of writing object-oriented code, I am now truely writing objects.
Dec 7, 2002 Pradeep Chandra (pradeep09@yahoo.com) from Des Moines,IA USA
Bible For Better Programming In Java
Fowler did a good job in writing this book, very nice to read with tons of examples as to how to refactor the code,
Nov 20, 2001 Mary from New Jersey
Great Book For every OO developer
I was fasinated by this book. It is the best book I read about OO development after years struggle with bad smell code. You can get a clear set of steps/strategy to improve the design and coding.
Nov 15, 2001 Anoosh Mostaghimi from San Jose, CA
Must read
One of the MOST practical and well-written Computer Science books I have ever read. Fowler has done a great job associating concepts with everyday code realities.
Mar 31, 2000 Tim Woodard (timw@dvc400.com) from Binghamton, NY
Very practical
This book is written in the style of design patterns. The concepts, however, are far less abstract than design patterns, so I found that I was able to start applying the refactorings immediately. A must read for anyone interesting in writing good software.
Nov 17, 1999 Glenn Carr (GlennCarr@email.com) from Tulsa, OK
Very good, practical book
Finally a book that captures what most good developers do anyway into a process and validates the practice. Very practical book. Fowler's writing style makes the book easy to read and entertaining at times.
|
|
