Comments on: Usul’s Words Have Power, Part 1: Refactor http://myotherpants.com/2009/09/usuls-words-part-1-refactor/ I left it in my other pants Wed, 19 May 2010 14:39:52 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Bruce http://myotherpants.com/2009/09/usuls-words-part-1-refactor/comment-page-1/#comment-8537 Bruce Wed, 19 May 2010 14:39:52 +0000 http://myotherpants.com/?p=150#comment-8537 Brian, great job at identifying the difference between redesign and refactoring. A term I like to use is what I call "opportunistic refactoring" (or drive-by refactoring) that is, if you're doing a feature that uses existing code, be on the look out for opportunities to refactore the existin code (rather than trying to shoe-horn the new feature into code that was created without that feature in mind). Also, you might want to look at JetBrain's RubyMine for Ruby refactoring support. Brian, great job at identifying the difference between redesign and refactoring. A term I like to use is what I call “opportunistic refactoring” (or drive-by refactoring) that is, if you’re doing a feature that uses existing code, be on the look out for opportunities to refactore the existin code (rather than trying to shoe-horn the new feature into code that was created without that feature in mind).

Also, you might want to look at JetBrain’s RubyMine for Ruby refactoring support.

]]> By: Michael Brown http://myotherpants.com/2009/09/usuls-words-part-1-refactor/comment-page-1/#comment-1227 Michael Brown Sat, 03 Oct 2009 17:32:22 +0000 http://myotherpants.com/?p=150#comment-1227 Brian, great job at identifying the difference between redesign and refactoring. A term I like to use is what I call "opportunistic refactoring" (or drive-by refactoring) that is, if you're doing a feature that uses existing code, be on the look out for opportunities to refactore the existin code (rather than trying to shoe-horn the new feature into code that was created without that feature in mind). Also, you might want to look at JetBrain's RubyMine for Ruby refactoring support. Brian, great job at identifying the difference between redesign and refactoring. A term I like to use is what I call “opportunistic refactoring” (or drive-by refactoring) that is, if you’re doing a feature that uses existing code, be on the look out for opportunities to refactore the existin code (rather than trying to shoe-horn the new feature into code that was created without that feature in mind).

Also, you might want to look at JetBrain’s RubyMine for Ruby refactoring support.

]]> By: Ball http://myotherpants.com/2009/09/usuls-words-part-1-refactor/comment-page-1/#comment-1181 Ball Mon, 28 Sep 2009 12:45:17 +0000 http://myotherpants.com/?p=150#comment-1181 Rachel, In the last few years, I've been bouncing from project to project, mostly to different environments. Some have excellent refactoring support and some have almost none. I feel that you don't <em>need</em> it. But it helps. To offer an analogy, I can build a bookcase with a handsaw, but a few power tools make it both practical and easier to get right. My friends can't say enough about <a href="http://www.jetbrains.com/resharper/" rel="nofollow">Resharper</a> from JetBrains (they got in the door by giving <a href="http://indyalt.net" rel="nofollow">IndyALT.NET</a> some licenses.) I started exploring Devexpress's <a href="http://www.devexpress.com/Products/Visual_Studio_Add-in/CodeRushX/" rel="nofollow">CodeRush Xpress</a> after hearing Hanselman talk about it. I'm not using it day-to-day because I'm currently on a regulated project and we'd have to verify it. I like what I see so far (and this is Rachel's product judging by her email address). The refactoring support for Java in Eclipse is great. TestComplete's JScript environment has no refactoring support, but its recorded test steps make it critical. The generated code is <em>legacy</em> by default. Ruby and VIM don't have any out of the box refactoring support. I'm a fan of tools but, as my woodworking career can attest, tool envy can block you from doing anything but yearn for a <em>real</em> table saw. On the other hand, a good tool can lower the barrier to good practice and make it more likely you'll do the right thing. Rachel,
In the last few years, I’ve been bouncing from project to project, mostly to different environments. Some have excellent refactoring support and some have almost none. I feel that you don’t need it. But it helps. To offer an analogy, I can build a bookcase with a handsaw, but a few power tools make it both practical and easier to get right.

My friends can’t say enough about Resharper from JetBrains (they got in the door by giving IndyALT.NET some licenses.)

I started exploring Devexpress’s CodeRush Xpress after hearing Hanselman talk about it. I’m not using it day-to-day because I’m currently on a regulated project and we’d have to verify it. I like what I see so far (and this is Rachel’s product judging by her email address).

The refactoring support for Java in Eclipse is great.

TestComplete’s JScript environment has no refactoring support, but its recorded test steps make it critical. The generated code is legacy by default.

Ruby and VIM don’t have any out of the box refactoring support.

I’m a fan of tools but, as my woodworking career can attest, tool envy can block you from doing anything but yearn for a real table saw. On the other hand, a good tool can lower the barrier to good practice and make it more likely you’ll do the right thing.

]]> By: Rachel http://myotherpants.com/2009/09/usuls-words-part-1-refactor/comment-page-1/#comment-1180 Rachel Mon, 28 Sep 2009 11:44:48 +0000 http://myotherpants.com/?p=150#comment-1180 Hi Brian, I am interested to know whether you suggest using 3rd party tools to refactor, or indeed if you personally use any 3rd party tools to get the job done? Great post, I particularly like the cake analogy, Rachel. Hi Brian,

I am interested to know whether you suggest using 3rd party tools to refactor, or indeed if you personally use any 3rd party tools to get the job done?

Great post, I particularly like the cake analogy,
Rachel.

]]>