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.

0201485672B04062001

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 139 Ratings

Must have in any developers collection - 2008-05-16
Reviewer Rating:
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.

Great Mentoring... - 2009-09-14
Reviewer Rating:
I learned many things from this book. After reading, I felt like that I had received years of mentoring from an experienced professional. I spent one week reading this on the subway and advanced two years in professional knowledge. Time and money well spent.

Refactoring - 2008-03-09
Reviewer Rating:
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.

Good resource for teaching - 2008-05-27
Reviewer Rating:
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.

An Easy Read - Lots of Great Info - Must for New Programmers - 2008-01-07
Reviewer Rating:
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.

Browse Similar Topics

Top Level Categories:
Software Engineering

Sub-Categories:
Software Engineering > OOP