Comments on: Making Refactoring Sexy… http://onemanswalk.com/work/2010/07/23/making-refactoring-sexy/ jeremy lightsmith on agile, ruby, and consulting Thu, 14 Jul 2011 22:58:42 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Ville Oikarinen http://onemanswalk.com/work/2010/07/23/making-refactoring-sexy/comment-page-1/#comment-178 Ville Oikarinen Thu, 29 Jul 2010 06:35:47 +0000 http://onemanswalk.com/work/?p=220#comment-178 You should just keep on doing what you do, preferably pairing with your colleagues. If none of them will eventually get it, then the problem is not the "how" you are showing them, it's the "what", and there is nothing that can be done to help them. The first level are the "trivial" refactorings that simply save (a lot of) keystrokes. I don't think it's difficult for them to appreciate them. But when someone sees a simple refactoring create an opportunity for a new refactoring, he'll start to get addicted. And when a series of simple refactorings create an opportunity to easily add behaviour/fix bugs (that have been pending as too difficult), you're done. It may be a long road, but what do you have to lose? If not anything else, you can keep on doing what you know to help yourself. You should just keep on doing what you do, preferably pairing with your colleagues. If none of them will eventually get it, then the problem is not the “how” you are showing them, it’s the “what”, and there is nothing that can be done to help them.

The first level are the “trivial” refactorings that simply save (a lot of) keystrokes. I don’t think it’s difficult for them to appreciate them. But when someone sees a simple refactoring create an opportunity for a new refactoring, he’ll start to get addicted. And when a series of simple refactorings create an opportunity to easily add behaviour/fix bugs (that have been pending as too difficult), you’re done.

It may be a long road, but what do you have to lose? If not anything else, you can keep on doing what you know to help yourself.

]]>