Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.
Download to your computer
Kindle Cloud Reader

Refactoring: Improving the Design of Existing Code 1st Edition

by
Martin Fowler (Author)
› Visit Amazon's Martin Fowler Page
Find all the books, read about the author, and more.
See search results for this author
Are you an author? Learn about Author Central
Martin Fowler (Author),
Kent Beck (Author)
› Visit Amazon's Kent Beck Page
Find all the books, read about the author, and more.
See search results for this author
Are you an author? Learn about Author Central
Kent Beck (Author), John Brant (Author),
4.5 out of 5 stars 204 customer reviews
ISBN-13: 978-0201485677
ISBN-10: 0201485672
Why is ISBN important?
ISBN
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
Trade in your item
Get a $16.94
Gift Card.
Trade in
Learn More
Have one to sell? Sell on Amazon

Sorry, there was a problem.

There was an error retrieving your Wish Lists. Please try again.

Sorry, there was a problem.

List unavailable.
Facebook Twitter Pinterest <Embed>
Buy used On clicking this link, a new layer will be open
$32.28 On clicking this link, a new layer will be open
Buy new On clicking this link, a new layer will be open
$49.86 On clicking this link, a new layer will be open
More Buying Choices
64 New from $34.98 58 Used from $32.28
122 used & new from $32.28
See All Buying Options
| Try Fast, Free Shipping
Amazon Prime members enjoy:
  • FREE Two-Day shipping on millions of items
  • Thousands of movies and TV shows with Prime Video
  • Over one million ad-free songs on Prime Music
  • Unlimited photo storage with Prime Photos
Try Prime
Free Two-Day Shipping for College Students with Prime Student Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student

Free Kaplan PSAT/NMSQT 2017 eTextbook with 2 Practice Tests
Prep smarter, not harder with the Kaplan "PSAT/NMSQT 2017 Strategies, Practice & Review" eTextbook. Sponsored by Kaplan. Download Now
$49.86 FREE Shipping. In Stock. Ships from and sold by Amazon.com. Gift-wrap available.
click to open popover

Frequently Bought Together

  • Refactoring: Improving the Design of Existing Code
  • +
  • Design Patterns: Elements of Reusable Object-Oriented Software
  • +
  • Clean Code: A Handbook of Agile Software Craftsmanship
Total price: $132.32
Buy the selected items together

Customers Viewing This Page May Be Interested In These Sponsored Links

  (What's this?)
NO_CONTENT_IN_FEATURE
New York Times best sellers
Browse the New York Times best sellers in popular categories like Fiction, Nonfiction, Picture Books and more. See more

Product Details

  • Hardcover: 464 pages
  • Publisher: Addison-Wesley Professional; 1 edition (July 8, 1999)
  • Language: English
  • ISBN-10: 0201485672
  • ISBN-13: 978-0201485677
  • Product Dimensions: 7.7 x 1.2 x 9.3 inches
  • Shipping Weight: 2.3 pounds (View shipping rates and policies)
  • Average Customer Review: 4.5 out of 5 stars  See all reviews (204 customer reviews)
  • Amazon Best Sellers Rank: #10,582 in Books (See Top 100 in Books)

    •  Would you like to update product info or give feedback on images?

Customers Viewing This Page May Be Interested In These Sponsored Links

  (What's this?)

Customer Reviews

Top Customer Reviews

4.0 out of 5 starsRecipes for improving code
By Sean Kelly on May 5, 2000
Format: Hardcover
Like the Gang of Four's landmark book _Design Patterns_, Fowler and his cohorts have created another catalog-style book, this time on refactoring.
Refactoring refers to taking existing, working software, and changing it about to improve its design, so that future modifications and enhancements are easier to add. _Refactoring_ is primarily a catalog of 70 or so different kinds of improvements you can make to object-oriented software.
Each entry in the catalog describes an implementation problem, the solution, motivation for applying the solution, the mechanics of the refactoring, and examples. The book's examples are all in Java, but C++ programmers should be able to approach the refactorings with ease. Often, Fowler diagrams the refactorings in UML, so a little Unified Modeling Language experience will help, too.
While the catalog is nice, the kinds of refactorings are obvious is most cases. Even moderately experienced programmers won't need the step-by-step mechanics described. The real benefit, though, is that the mechanics of each refactoring help guarantee that you can pull off the refactoring without introducing new bugs or side effects. They encourage you to take smaller, verifiable steps, than the more gross refactorings that most developers would naturally take. You actually save time doing so.
How do you know your refactorings are safe? Unit testing is the answer that Fowler et al. provide. Java developers will find the introduction to the Junit Testing Framework the most valuable part of the book, more so than the catalog of refactorings itself.
There's more to the book than the catalog and Junit, of course.Read more ›
Comment 162 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
5.0 out of 5 starsRefactoring: Improving the Design of Existing Code
By Christopher Taylor on November 11, 2002
Format: Hardcover
A little while back I was introduced to a word I had never heard before, Refactoring. I was told to
get Martin Fowler's book and read it so I could gain a better understanding of what Refactoring
was. Well folks, I would classify this book as a 'Hidden Treasure'.
Although it is not a flashy or well known title, I believe its impact can be much deeper and long
lasting than many of the mainstream, more popular technology books. The underlying theories
that it teaches can be applied for years, even when languages change.
There are only a couple of things I would change about this book, which I will mention below.
Preface
The Preface it brief enough, and gives the definition for the word Refactoring. This is a good thing
because right form the start you get the true definition of Refactoring. In short, refactoring is the
process of changing code to improve the internal structure, but not changing the external
behavior.
Chapter 1: Refactoring, a First Example
In this chapter Mr. Fowler tries to start by showing a simple Refactoring example. The problem is
that the chapter then goes on for 50+ pages. Mr. Fowler explains his reasons for doing this, but I
think that a simple example should have been much simpler. Especially when it is in the first
chapter of the book. It's not that this isn't a good chapter. I feel it's just too soon in the book. I
would have put it at the end.
Chapter 2: Principles of Refactoring
This is an excellent chapter. The definition of Refactoring is discussed as well as the following
questions: Why should you refactor? When should you refactor? What do I tell my manager?Read more ›
Comment 115 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
5.0 out of 5 starsMaking tired old code better
By Amazon Customer on May 17, 2000
Format: Hardcover
The basic thesis of this book is that, for various reasons, real programs are poorly designed. They get that way for a variety of reasons. Initially well designed, extending the program may lead to software decay. Huge methods may result from unanticipated complexity. Refactoring, according to Fowler, is a function preserving transformation of a program. The transformations are reversible, so the intention is to improve the program in some way.
Fowler suggests refactoring a program to simplify the addition of new functionality. The program should also be refactored to make it easier for human readers to understand at the same time.
He also insists that each step is small and preserves functionality, and on frequent unit testing with a comprehensive test suite.
Half of the book consists of a catalogue of refactorings. He gives each refactoring a memorable name, such as "Replace Type Code with Subclasses". He illustrates the design transformation with a pair of UML class diagrams, and has a standard set of sections: Motivation, Mechanics and Example.
The Motivation is a prose section that describes and justifies the refactoring, showing the relationship to other refactorings.
The Mechanics is a sequence of steps needed to carry out the refactoring, shown as a list of bullet points He expands on some points.
The Example is where the value of this book lies. Fowler takes a fragment of Java code, and takes us step by step through the refactoring. The code is small enough that he can show it all each step of the way without overwhelming us, but is large enough to be realistic.
The code is clear enough for non-Java programmers to follow.Read more ›
Comment 28 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse

Most Recent Customer Reviews

5.0 out of 5 starsJust get a copy...

A classic that no beginning Java programmer should be without.

Published 15 days ago by Amazon Customer
5.0 out of 5 starsFive Stars

As advertised

Published 2 months ago by Amazon Customer
5.0 out of 5 starsEnable your code to evolve

I have been actually refactoring (renaming variables, and moving functions among classes) using C++ for a while but never think through it systematically, which makes me always... Read more

Published 2 months ago by Sean
5.0 out of 5 starsA thoroughly entertaining treatment of what could be a dry topic

The authors need to be congratulated and thanked for their humorous and engaging presentation of what could have been a long dry and dreary list of dos and don'ts. Read more

Published 4 months ago by Shivesh K Suman
5.0 out of 5 starsMust read for any serious software engineer

Must read for any serious software engineer. Once you've supported a project long enough to see the code decay, you should read this to develop a methodical way of... Read more

Published 6 months ago by Nels Wadycki
4.0 out of 5 starsFour Stars

Excellent resource for improving legacy code.

Published 7 months ago by amazonbuster
5.0 out of 5 starsthe hardcover paper book is a great reference, much better (for me at...

I believe every professional programmer should know the book. Although there is an on-line version, the hardcover paper book is a great reference, much better (for me at least ) to... Read more

Published 7 months ago by A. Kucharczyk
4.0 out of 5 starsGreat unlessb you have object design experience. Good for an IT...

I found this stuff to be obvious but the older top down coders trying to change their ways and learn object driven design love it.

Published 7 months ago by Witt
5.0 out of 5 starsFive Stars

A must have for every programmers.

Published 7 months ago by Berk
4.0 out of 5 starsFour Stars

Showed up in good condition, just fairly worn in

Published 7 months ago by Wes Draper

Set up an Amazon Giveaway

Refactoring: Improving the Design of Existing Code
Amazon Giveaway allows you to run promotional giveaways in order to create buzz, reward your audience, and attract new followers and customers. Learn more about Amazon Giveaway
This item: Refactoring: Improving the Design of Existing Code
Set up a giveaway

There's a problem loading this menu right now.

Learn more about Amazon Prime.