30 days return. Buyer pays for return postage. If you use an eBay delivery label, it will be deducted from your refund amount.
Condition:
Very GoodVery Good
Refactoring Workbook (Addison-wesley Object Technology Series). Author:Wake, William. General Interest. We all like the idea of saving a bit of cash, so when we found out how many good quality used products are out there - we just had to let you know!
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
About this product
Product Identifiers
PublisherAddison Wesley Professional
ISBN-100321109295
ISBN-139780321109293
eBay Product ID (ePID)2361193
Product Key Features
Number of Pages256 Pages
LanguageEnglish
Publication NameRefactoring Workbook
SubjectGeneral, Software Development & Engineering / Systems Analysis & Design
Publication Year2003
TypeTextbook
AuthorRoss Ross Venables, William Wake
Subject AreaComputers
FormatTrade Paperback
Dimensions
Item Height0.6 in
Item Weight17.6 Oz
Item Length9.2 in
Item Width7.6 in
Additional Product Features
Intended AudienceScholarly & Professional
LCCN2003-057903
Dewey Edition22
Dewey Decimal005.1/6
Table Of ContentPreface. 1. Roadmap. Overview. Section 1: Smells within Classes. Section 2: Smells between Classes. Section 3: Programs to Refactor. A Word on the Challenges. I. SMELLS WITHIN CLASSES. 2. The Refactoring Cycle. What Is Refactoring? Smells Are Problems. The Refactoring Cycle. When Are We Done? Inside a Refactoring. Challenges. Conclusion. 3. Measured Smells. Smells Covered. Comments. Long Method. Large Class. Long Parameter List. More Challenges. Conclusion. Interlude 1. Smells and Refactorings. 4. Names. Smells Covered. Type Embedded in Name (Including Hungarian). Uncommunicative Name. Inconsistent Names. 5. Unnecessary Complexity. Smells Covered. Dead Code. Speculative Generality. Interlude 2. Inverses. 6. Duplication. Smells Covered. Magic Number. Duplicated Code. Alternative Classes with Different Interfaces. Challenges. 7. Conditional Logic. Smells Covered. Null Check. Complicated Boolean Expression. Special Case. Simulated Inheritance (Switch Statement). Interlude 3. Design Patterns. II. SMELLS BETWEEN CLASSES. 8. Data. Smells Covered. Primitive Obsession. Data Class. Data Clump. Temporary Field. 9. Inheritance. Smells Covered. Refused Bequest. Inappropriate Intimacy (Subclass Form). Lazy Class. 10. Responsibility. Smells Covered. Feature Envy. Inappropriate Intimacy (General Form). Message Chains. Middle Man. Challenges. 11. Accommodating Change. Smells Covered. Divergent Change. Shotgun Surgery. Parallel Inheritance Hierarchies. Combinatorial Explosion. 12. Library Classes. Smells Covered. Incomplete Library Class. Challenges. Interlude 4. Gen-A-Refactoring. III. PROGRAMS TO REFACTOR. 13. A Database Example. Course.java (Online at www.xp123.com/rwb). Offering.java. Schedule.java. Report.java. TestSchedule.java. TestReport.java. 14. A Simple Game. Development Episodes. 15. Catalog. Introduction. Path 1: Catalog.itemsMatching(query). Path 2: Query.matchesIn(catalog). Path 3: Process(catalog.data, query.data). Conclusion. 16. Planning Game Simulator. Part 1: Original Code. Part 2: Redistributing Features. Removing Duplication, Selection Troubles, and a Few Burrs. Part 3: Pushing the Code Further. 17. Where to Go from Here. Books. Admonitions. Exercises to Try. Web Sites. IV. APPENDIXES. A: Answers to Selected Questions. B: Java Refactoring Tools. C: Inverses for Refactorings. D: Key Refactorings. Bibliography. Index.
SynopsisThis example-driven workbook shows how to unleash the significant power of refactoring and improve your software. It aims to help identify where problems in a software application exist or are likely to exist., Refactoring has gained widespread acceptance in the software engineering community as a proven means of improving software. Martin Fowler's seminal book on this topic, Refactoring , 0201485672, has been used in the classroom to explain that existing code could be improved and enhanced without significantly altering the fundamental structure of an application. But many find that this concept has a steep learning curve that inhibits its use. In this new book, William Wake offers a more introductory look at this important topic. The author outlines a proven workbook approach to learning and applying refactoring to "everyday" projects. This approach relies on examples that force the student to apply the main concepts of refactoring. As a result, readers gain thorough knowledge of how refactoring can help improve their software.