|
Loading... Refactoring: Improving the Design of Existing Codeby Martin Fowler
LibraryThing recommendationsMember recommendationsLoading...
won't like
will probably not like
will probably like
will like
will love Sign up for LibraryThing to find out whether you'll like this book.  euang | Sep 1, 2008 |  Owner: TG  transmissiongames | Jun 3, 2008 | If you write any code at all, anywhere, read this book. Refactoring should be an integral part of all coding efforts, and this book does a marvelous job of conveying the mechanics and theory of such things through clear prose and many examples. (  )1  akbibliophile | Jul 20, 2007 | oxtremists | Nov 23, 2006 | Refactoring is the act of restructuring source code without changing its behavior: you refactor the code so that it is easier to modify in the future. Fowler describes a number of different kinds of refactorings, with explicit instructions on how to apply these refactorings. (  ) lorin | May 19, 2006 |  no reviews | add a review
Amazon.com (ISBN 0201485672, Hardcover)Your class library works, but could it be better? Refactoring: Improving the Design of Existing Code shows how refactoring can make object-oriented code simpler and easier to maintain. Today refactoring requires considerable design know-how, but once tools become available, all programmers should be able to improve their code using refactoring techniques.Besides an introduction to refactoring, this handbook provides a catalog of dozens of tips for improving code. The best thing about Refactoring is its remarkably clear presentation, along with excellent nuts-and-bolts advice, from object expert Martin Fowler. The author is also an authority on software patterns and UML, and this experience helps make this a better book, one that should be immediately accessible to any intermediate or advanced object-oriented developer. (Just like patterns, each refactoring tip is presented with a simple name, a "motivation," and examples using Java and UML.) Early chapters stress the importance of testing in successful refactoring. (When you improve code, you have to test to verify that it still works.) After the discussion on how to detect the "smell" of bad code, readers get to the heart of the book, its catalog of over 70 "refactorings"--tips for better and simpler class design. Each tip is illustrated with "before" and "after" code, along with an explanation. Later chapters provide a quick look at refactoring research. Like software patterns, refactoring may be an idea whose time has come. This groundbreaking title will surely help bring refactoring to the programming mainstream. With its clear advice on a hot new topic, Refactoring is sure to be essential reading for anyone who writes or maintains object-oriented software. --Richard Dragan Topics Covered: Refactoring, improving software code, redesign, design tips, patterns, unit testing, refactoring research, and tools. (retrieved from Amazon Fri, 24 Apr 2009 07:58:15 -0400) The first test round has been closed. Visit the Open Shelves Classification group for details. |
Abebooks |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> Remove duplicated code
> Write smaller classes "Do one thing and do it well"
> Only expose methods that need to be exposed
> re-write complicated expressions by introducing temporary variables with names that explain the purpose
and so many others. Particularly great for those left maintaining code written by someone else who thought a class containing 2,500 lines of code is fine.