In my experience, design reuse is often far more helpful and practical than actual reuse of code.
I definately agree. "Reuse Hysteria" should shift focus from code to design. Reusing human intelligence is more abstract, can be applied to nearly any development enviornment and deals with the problems that are usually much more difficult and costly than implementation. Broken pieces can always be fixed, broken designs are far more costly problems to deal with.
I am only saying the emphasis is in the wrong place because code reuse can definately help, I've used CPAN too many times to try an shortchange the benefits of code reuse. If only there was something as well put together and concise as CPAN for design reuse.
Unfortunately in CS programs "Design Reuse" is often seen as cheating, and any design reuse should come from personal experience.
Fortunately, open source software creates an excellent enviornment for promoting design reuse.
Slashdot Mirror
In my experience, design reuse is often far more helpful and practical than actual reuse of code.
I definately agree. "Reuse Hysteria" should shift focus from code to design. Reusing human intelligence is more abstract, can be applied to nearly any development enviornment and deals with the problems that are usually much more difficult and costly than implementation. Broken pieces can always be fixed, broken designs are far more costly problems to deal with.
I am only saying the emphasis is in the wrong place because code reuse can definately help, I've used CPAN too many times to try an shortchange the benefits of code reuse. If only there was something as well put together and concise as CPAN for design reuse.
Unfortunately in CS programs "Design Reuse" is often seen as cheating, and any design reuse should come from personal experience.
Fortunately, open source software creates an excellent enviornment for promoting design reuse.