| Refactoring: Improving the Design of Existing Code (Addison-Wesley Object Technology Series) | 
 enlarge | List Price: $59.99
Buy New: $35.90
You Save: $24.09 (40%)
Buy New/Used from $31.65
Avg. Customer Rating:   (based on 138 reviews)
Sales Rank: 23535
Category: Book
Authors: Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts
Publisher: Addison-Wesley Professional
Studio: Addison-Wesley Professional
Manufacturer: Addison-Wesley Professional
Label: Addison-Wesley Professional
Languages: English (Original Language), English (Unknown), English (Published)
Media: Hardcover
Number Of Items: 1
Pages: 464
Shipping Weight (lbs): 2.7
Dimensions (in): 9.3 x 7.6 x 1.3
ISBN: 0201485672
Dewey Decimal Number: 005.14
UPC: 785342485677
EAN: 9780201485677
ASIN: 0201485672
Publication Date: July 8, 1999
Availability: Usually ships in 1-2 business days
|
| Accessories:
|
| Similar Items:
|
| Editorial Reviews:
Product Description
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 Software, 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.
Amazon.com Review
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.
|
| Customer Reviews: Read 133 more reviews...
 Good resource for teaching May 27, 2008
What is better? Replacing delegations with inheritance or replacing inheritance with delegation?
The answer is the ultimate answer to most software engineering decisions: DEPENDS, there is always a trade-off that has to be analyzed according to the context! This book addresses those trade-offs very well.
Moreover, I like the examples in the book, good to use in class when teaching. They generate interesting discussions.
 Must have in any developers collection May 16, 2008
1 out of 1 found this review helpful
I was referred to this book from a colleague after a quick discussion on "Replace temp with Query" in our projects code base.
I thought I knew it all as a software developer, but reading this book, I soon came to realize that as a software developer I was leaving a legacy of code that was not at the standard it should be.
This book opened my eyes to some really simple concepts, for example, when trying to understand code someone else has written (or yourself in some cases) take the time to re-factor the code (i.e. Extract Method) so that the code is understandable, since most of the work is spent in trying to understand the code in the first place. This concept of modifying code as you understand it is superb.
I must say I was skeptical at first but the benefits are really starting to show. This book is written with the knowledge of Martin Fowler, and as such is written with experience of what it is like to be a developer in a commercial environment, for example, trying to explain to management the trade-offs of re-factoring first instead of "tacking on" that new feature. Something that is difficult in any environment.
This book will by no means solve your problems, but it will empower you with a new found love to make the IT project(s) you work on better (i.e. not thinking of the now but the future) practice some of the smaller concepts this book presents on a daily basis and the rewards are well worth it, break those bad habits today.
Refactoring March 9, 2008
1 out of 1 found this review helpful
Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure. It is a disciplined way to clean up code that minimizes the chances of introducing bugs. In essence when you refractor you are improving the design of the code after it has been written.
When I first got this hardcover in December 2000, there were no integrated development environments (IDE) that would have easily allowed applying refactorings like Extract Method or Inline Method. Now, in 2008, any IDE like Delphi allows to refactor in one click. So now this book is even more valuable than it was at a time of first publication.
An Easy Read - Lots of Great Info - Must for New Programmers January 7, 2008
This book is just a real easy read, with lots of good information. You can pretty much flip to any page in the book, read, and learn something. You don't have to read chapter by chapter - it's just real easy to jump into.
Lots of tips seem self-evident, but I doubt they would be to rookie programmers. It's definitely a book new programmers should get their hands on early.
A must read for any serious developer. November 23, 2007
1 out of 1 found this review helpful
This book is required reading for anyone who is serious about software development. If you want to go from good to great then do yourself a favor and get this book.
|
|
|
