Refactoring: The Book that Changed Everything for Me

Disclosure: The book links below are affiliate links. If you buy anything, I earn a commission, at no extra cost to you.

Slogging through code is what we do for a living. What would you give to be able to improve your existing codebase?

Refactoring book

The Refactoring book completely changed the way I code.

In 2001 while searching for information on design patterns, I discovered the original wiki, and stumbled on Extreme Programming. This led me to a software development conference in 2002 called SD West. There I attended a session by Martin Fowler, and knew that I had to pick up his Refactoring book that day.

How could I resist a book that promised to teach me about “improving the design of existing code”?

Refactoring: Co-opted in the workplace?

Many years later, I find the term “refactoring” being thrown around in the workplace, at several software companies. Programmers and managers often talk about “refactoring,” when they usually just mean “rewriting.” I’ve seen nightmares brought about by so-called “refactoring” that introduced so many defects, it compromised the product ship date.

The Refactoring book, however, teaches a disciplined methodology of changing code in small steps, with automated verification of each step.

Of the books I keep at work, a small handful are kept within easy reach for looking things up. This is one of those books. Each refactoring has a detailed recipe of its steps, and things go better when I open the book to follow those precise steps.

If my statement that it “completely changed the way I code” seems like hyperbole, another blogger states it even more strongly: “That moment changed my life.”

Would you like to transform ugly code to make it better, but do so safely? What are you waiting for… buy a copy of the Refactoring book today!


Question: What has been your experience with refactoring? Leave a comment below.

About the Author Jon Reid

I first experienced the joy of programming in junior high. But on the job, some of that joy was sucked away by seeing code my teammates were afraid to touch. Poor code led to fear, and fear led to our entire team being let go. I began searching for ways to improve code. I stumbled upon the first wiki, which was about Design Patterns, Extreme Programming, and Test Driven Development (TDD). I rediscovered joy on the job. I've now been doing TDD in Apple environments for 17 years. I'm committed to software crafting as a discipline, with the hope of raising you, my fellow programmers, to greater effectiveness and joy.

follow me on:
Disclosure: The links below are affiliate links. If you buy anything, I earn a commission, at no extra cost to you.
  • Herman says:

    Finally received my copy of Refactoring. The hardcover somehow reminds me of the time I was in college.
    Enjoy the rest of the weekend.

  • >