Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • +1, thanks. But, I believe I am fairly good at refactoring OO code with more OO code. What I don't know is how to test procedural code, and refactor procedural code with less coupled procedural code. Commented Aug 25, 2011 at 8:19
  • @Groo, the book is not about refactoring per se. It is about how to transform a bunch of spaghetti code without any unit tests into a bunch of (somewhat less spaghetti) code well covered with unit tests. Such code is hard to test, so you need to refactor first in order to make it testable; however, as you too mentioned, refactoring without unit tests is risky, so it is a catch 22 situation. The book guides you how to make the smallest, safest changes to the code which enable you to cover it with unit tests, thus subsequently start refactoring it in earnest. Commented Aug 25, 2011 at 8:27
  • That book is a good suggestion and it covers C along with OO languages. Commented Jan 11, 2012 at 0:02