Refactoring to Patterns (Hardcover)
貴賓價: $2,328Patterns of Enterprise Application Architecture (Hardcover)
售價: $1,733Code Complete: A Practical Handbook of Software Construction, 2/e (Paperback)
貴賓價: $2,161Refactoring: Improving the Design of Existing Code (Hardcover)
貴賓價: $1,710API Design for C++ (Paperback)
貴賓價: $1,796Head First Design Patterns (Paperback)
貴賓價: $1,663Test-Driven Development: By Example (Paperback)
貴賓價: $2,161Working Effectively with Legacy Code (Paperback)
貴賓價: $1,663Clean Code: A Handbook of Agile Software Craftsmanship (Paperback)
貴賓價: $2,195Design Patterns in Java, 2/e (Hardcover)
貴賓價: $1,881C++ Coding Standards: 101 Rules, Guidelines, and Best Practices (Paperback)
售價: $1,931Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages (Hardcover)
貴賓價: $1,957Design Patterns Explained: A New Perspective on Object-Oriented Design, 2/e (Paperback)
With the highly anticipated Refactoring to Patterns, Joshua Kerievsky has changed our approach to design by forever uniting patterns with the evolutionary process of refactoring.
Intended for the more experienced student, this book introduces the theory and practice of pattern-directed refactorings: sequences of low-level refactorings that allow designers to safely move designs to, towards, or away from pattern implementations. Using code from real-world projects, Kerievsky documents the thinking and steps underlying over two dozen pattern-based design transformations. Along the way he offers insights into pattern differences and how to implement patterns in the simplest possible ways.
Table of Contents:
Foreword by Ralph Johnson.
Foreword by Martin Fowler.
What Is This Book About?
What Are the Goals of This Book?
Who Should Read This Book?
What Background Do You Need?
How to Use This Book.
The History of This Book.
Standing on the Shoulders of Giants.
1. Why I Wrote This Book.
The Patterns Panacea.
Test-Driven Development and Continuous Refactoring.
Refactoring and Patterns.
What Is Refactoring?
What Motivates Us to Refactor?
Keeping It Clean.
Evolving a New Architecture.
Composite and Test-Driven Refactorings.
The Benefits of Composite Refactorings.
What Is a Pattern?
There Are Many Ways to Implement a Pattern.
Refactoring to, towards, and away from Patterns.
Do Patterns Make Code More Complex?
Up-Front Design with Patterns.
4. Code Smells.
Alternative Classes with Different Interfaces.
5. A Catalog of Refactorings to Patterns.
Format of the Refactorings.
Projects Referenced in This Catalog.
A Starting Point.
A Study Sequence.
Replace Constructors with Creation Methods.
Move Creation Knowledge to Factory.
Encapsulate Classes with Factory.
Introduce Polymorphic Creation with Factory Method.
Encapsulate Composite with Builder.
Replace Conditional Logic with Strategy.
Move Embellishment to Decorator.
Replace State-Altering Conditionals with State 166
Replace Implicit Tree with Composite.
Replace Conditional Dispatcher with Command.
Form Template Method.
Replace One/Many Distinctions with Composite.
Replace Hard-Coded Notifications with Observer.
Unify Interfaces with Adapter.
Replace Implicit Language with Interpreter.
Replace Type Code with Class.
Limit Instantiation with Singleton.
Move Accumulation to Collecting Parameter.
Move Accumulation to Visitor.
Afterword by John Brant and Don Roberts.