Comments on: Refactoring vs. Refuctoring http://www.klocwork.com/blog/2010/02/refactoring-vs-refuctoring/?utm_source=rss&utm_medium=rss&utm_campaign=refactoring-vs-refuctoring >kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis. Tue, 24 Jan 2012 14:57:13 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Alen Zukich http://www.klocwork.com/blog/2010/02/refactoring-vs-refuctoring/comment-page-1/#comment-1185 Alen Zukich Fri, 05 Feb 2010 17:04:06 +0000 http://www.klocwork.com/blog/?p=716#comment-1185 LOL...now that is a good Refuctoring LOL…now that is a good Refuctoring

]]> By: James http://www.klocwork.com/blog/2010/02/refactoring-vs-refuctoring/comment-page-1/#comment-1149 James Wed, 03 Feb 2010 21:32:19 +0000 http://www.klocwork.com/blog/?p=716#comment-1149 My favorite refuctoring (from personal experience): Instead of deleting unused code, control whether or not it is compiled using a well hidden #define. Using Makefile's include feature is ideal for this. When anyone tries to read your code, they will flip out in their cubicle when they realize that the code they have been reading for 10 minutes, "which shouldn't even work at all," really doesn't exist. My favorite refuctoring (from personal experience):

Instead of deleting unused code, control whether or not it is compiled using a well hidden #define. Using Makefile’s include feature is ideal for this. When anyone tries to read your code, they will flip out in their cubicle when they realize that the code they have been reading for 10 minutes, “which shouldn’t even work at all,” really doesn’t exist.

]]>