Refactoring: Turning Nightmares Into Minor Unpleasantness

Last updated: 3 months ago

We all see bad stuff we either inherited or wrote ourselves some time before. Without a plan, it can be quite the nightmare to try to fix without just lighting it all on fire. I’ll give some realistic examples of messes you can end up with and explain how to approach fixing them. There’s no one solution to fix all problems, but I do have a strategy that works fairly well.

I'll discuss issues such as:

  • Entirely too many subclasses
  • Giant view controllers
  • Projects with 4 different architectures used in different places
  • Projects that have ignored warnings
  • 30k+ lines of dead code
  • Massive frameworks like Three20