Comments on: Code Reuse: Pros and Cons http://jessewarden.com/2006/05/code-reuse-pros-and-cons.html A blog on software development, technology, games & movies. Thu, 20 Nov 2008 12:29:51 +0000 http://wordpress.org/?v=2.5 By: Mark Lapasa http://jessewarden.com/2006/05/code-reuse-pros-and-cons.html#comment-3535 Mark Lapasa Wed, 24 May 2006 17:45:26 +0000 http://jessewarden.com/?p=1015#comment-3535 Good article Jesse, 'Reusing code becomes more important that greater the size of the project, and/or in the frequency of projects.' I couldn't agree anymore. Processes like such become more and more relevant as the project or the development team grows. Good article Jesse,

‘Reusing code becomes more important that greater the size of the project, and/or in the frequency of projects.’

I couldn’t agree anymore. Processes like such become more and more relevant as the project or the development team grows.

]]> By: Brandon http://jessewarden.com/2006/05/code-reuse-pros-and-cons.html#comment-3534 Brandon Wed, 24 May 2006 17:36:51 +0000 http://jessewarden.com/?p=1015#comment-3534 Good points Jesse. I've always been big on code reuse. At one job though, I was working for a federal gov't contractor and the big boss always said 'code is cheap'. He loved making folks repeat code so that they could bill more hours to the gov't! I didn't last long there. :) Good points Jesse. I’ve always been big on code reuse. At one job though, I was working for a federal gov’t contractor and the big boss always said ‘code is cheap’. He loved making folks repeat code so that they could bill more hours to the gov’t! I didn’t last long there. :)

]]> By: JesterXL http://jessewarden.com/2006/05/code-reuse-pros-and-cons.html#comment-3533 JesterXL Wed, 24 May 2006 17:34:55 +0000 http://jessewarden.com/?p=1015#comment-3533 Thanks guys! James, I was honest about using the same preloader. What I didn't tell you was that's ALL I re-use. Every project, whether personal or profesional, I always seem to be creating new stuff. Yes, we use the same framework, and same approach for the most part, but most of the reuse seems to be per project, not across multiple projects up until very recently. The key is the try. Again, it doesn't matter if your classes are only used once and never again. The attitude you use in building them for reuse from the start is what produces simple, non-duplicated code. That's a great thing no matter how you look at it. Thanks guys!

James, I was honest about using the same preloader. What I didn’t tell you was that’s ALL I re-use. Every project, whether personal or profesional, I always seem to be creating new stuff.

Yes, we use the same framework, and same approach for the most part, but most of the reuse seems to be per project, not across multiple projects up until very recently.

The key is the try. Again, it doesn’t matter if your classes are only used once and never again. The attitude you use in building them for reuse from the start is what produces simple, non-duplicated code. That’s a great thing no matter how you look at it.

]]> By: TheElder http://jessewarden.com/2006/05/code-reuse-pros-and-cons.html#comment-3532 TheElder Wed, 24 May 2006 16:08:18 +0000 http://jessewarden.com/?p=1015#comment-3532 Great article! Very good read! I like how this can be applied to programming in general. The 'tools' example was a really good analogy. To expand upon that, I guess it works from a design perspective as well. In the beginning graphic artist tend to use the tools that are built into the software they are using. Like Photoshop has it's default Filters and you can get more filters from AlienSkin or whatever. After a while the designer grows and then realizes there are other brushes, patterns, etc. out there that they can use. Ultimately most end up making their own dynamic library of brushes, patterns, scripts, etc. The greats seem to have reusable tools and components (that accounts for their speed and effiicency) with MOTIVATED use of them (No more lens flares for the hell of it). Great article! Very good read! I like how this can be applied to programming in general.

The ‘tools’ example was a really good analogy. To expand upon that, I guess it works from a design perspective as well.

In the beginning graphic artist tend to use the tools that are built into the software they are using. Like Photoshop has it’s default Filters and you can get more filters from AlienSkin or whatever. After a while the designer grows and then realizes there are other brushes, patterns, etc. out there that they can use. Ultimately most end up making their own dynamic library of brushes, patterns, scripts, etc.

The greats seem to have reusable tools and components (that accounts for their speed and effiicency) with MOTIVATED use of them (No more lens flares for the hell of it).

]]> By: James Hay http://jessewarden.com/2006/05/code-reuse-pros-and-cons.html#comment-3531 James Hay Wed, 24 May 2006 11:27:05 +0000 http://jessewarden.com/?p=1015#comment-3531 Thats a great article Jester.. thanks. I must say i'm in my first real AS2.0 OOP role at Magic Lantern and i'm having to start thinking about resuability of my classes for the first time. I must say it's harder than it seems and i'm definatley making a few mistakes along the way (some of my earlier stuff is not reuasable in any shape or form). One thing thats definately helped me is learning to use design patterns more often (at the moment singletons, factory and MVC). Still think i've got a long way to go and a fair bit to learn before i'm writing classes that are as reuasable and as efficient as possible but i suppose that comes with experience. Thanks again for a good read James Thats a great article Jester.. thanks. I must say i’m in my first real AS2.0 OOP role at Magic Lantern and i’m having to start thinking about resuability of my classes for the first time. I must say it’s harder than it seems and i’m definatley making a few mistakes along the way (some of my earlier stuff is not reuasable in any shape or form). One thing thats definately helped me is learning to use design patterns more often (at the moment singletons, factory and MVC). Still think i’ve got a long way to go and a fair bit to learn before i’m writing classes that are as reuasable and as efficient as possible but i suppose that comes with experience.

Thanks again for a good read

James

]]>