Comments on: Copy And Paste And Bugs http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/ ASP.NET, HTML, CSS, Visual Studio, CSharp, VB.NET and other programming items of interest. Mon, 15 Mar 2010 11:52:22 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Dave http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/comment-page-1/#comment-3467 Dave Tue, 15 Sep 2009 16:16:15 +0000 http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/#comment-3467 Right, that's why I end with "Sometimes copy and paste can't be avoided..." It's a call to be intentional about NOT creating the method or function rather than not creating it by default. Right, that’s why I end with “Sometimes copy and paste can’t be avoided…”

It’s a call to be intentional about NOT creating the method or function rather than not creating it by default.

]]> By: Karl Agius http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/comment-page-1/#comment-3466 Karl Agius Tue, 15 Sep 2009 16:04:12 +0000 http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/#comment-3466 I get what you mean about troubleshooting and cleaning up. I'm just a bit wary of advocating the 'avoid duplication at all costs' approach because it can lead to a mess just as much as inconsiderate duplication - say, methods with names that have nothing to do with the context they're being used in, weird hacks to existing methods that break more stuff, and so on. Something's always got to give; if someone doesn't take enough pride in their work to do things properly, forcing one side will break the other. I take it that your post is more aimed towards sloppy coding in general, lack of testing, not enough expression of intent in code, and all those things which make a maintainer/troubleshooter's life so interesting; I definitely have to agree with you completely there. I get what you mean about troubleshooting and cleaning up. I’m just a bit wary of advocating the ‘avoid duplication at all costs’ approach because it can lead to a mess just as much as inconsiderate duplication – say, methods with names that have nothing to do with the context they’re being used in, weird hacks to existing methods that break more stuff, and so on. Something’s always got to give; if someone doesn’t take enough pride in their work to do things properly, forcing one side will break the other.

I take it that your post is more aimed towards sloppy coding in general, lack of testing, not enough expression of intent in code, and all those things which make a maintainer/troubleshooter’s life so interesting; I definitely have to agree with you completely there.

]]> By: Dave http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/comment-page-1/#comment-3465 Dave Tue, 15 Sep 2009 15:41:41 +0000 http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/#comment-3465 Unfortunately, step three never happens for most of us. While simply spending a bit more time AS YOU WRITE would solve the main problem in the first place. Not using duplication analysis tool right now. But that's more a factor of either having NO control over the code base I'm working with/on. I'm a trouble shooter. Rarely is finding duplicate code the solution to the problem, even though duplicating code IS often the cause. That is, I get called in to find the problem and fix it, not to clean up the entire code base.. although that may be a recommendation that I make along the way. Unfortunately, step three never happens for most of us. While simply spending a bit more time AS YOU WRITE would solve the main problem in the first place.

Not using duplication analysis tool right now. But that’s more a factor of either having NO control over the code base I’m working with/on.

I’m a trouble shooter. Rarely is finding duplicate code the solution to the problem, even though duplicating code IS often the cause. That is, I get called in to find the problem and fix it, not to clean up the entire code base.. although that may be a recommendation that I make along the way.

]]> By: Karl Agius http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/comment-page-1/#comment-3464 Karl Agius Tue, 15 Sep 2009 15:21:06 +0000 http://blog.dmbcllc.com/2009/09/15/copy-and-paste-and-bugs/#comment-3464 I feel your pain, as I'm sure most coders out here do. As much as I hate copy/pasting though, I do feel that Fowler's rule of three (the first time you write, the second time you duplicate, the third time you refactor) makes a lot more sense than always creating a method, class, or component to avoid duplication. That way lies a massively bloated code base. On another note, do you use any code duplication analysis tools, and if so, which? Thanks for the post :) I feel your pain, as I’m sure most coders out here do.

As much as I hate copy/pasting though, I do feel that Fowler’s rule of three (the first time you write, the second time you duplicate, the third time you refactor) makes a lot more sense than always creating a method, class, or component to avoid duplication. That way lies a massively bloated code base.

On another note, do you use any code duplication analysis tools, and if so, which?

Thanks for the post :)

]]>