Refactoring goodness

Today I spent some time in our code at work (I know…shocking that I was writing code).  One of the things that I found was a group of three files that each contained anywhere from 3 to 20 public classes.  I’m at the point where this is no longer shocking and instead I just turn to immediately looking to refactor instead.  While I was hammering through the process of changing the namespace, moving to a new file (thank you Resharper F6!) and physically moving the files, the ease of the process struck me with a thought.  Resharper is not just a great tool for refactoring.  It’s a tool for placating your worries about the difficulty of the refactoring.

If I had not had Resharper to help with this process I very well might have looked at the class and then walked away from it thinking (more likely muttering) about the difficulty of fixing someone’s past indiscretions.  Resharper gives developers the piece of mind to make significant changes with little effort impact.  That, plus the consistently error free results, makes the decision to improve the code so much simpler.

I did run into one small issue with the refactoring at work on v2.5 of Resharper, but when I tried it at home I was unable to reproduce it with v3.0.  All good in my books.