At my company we use common libraries, share various business backends and reuse internally developer frameworks. Current level of code reuse is not perfect of course, i.e. the Java component model is extremely weak and the language doesn't facilitate as much reuse as certain other languages. It does have Maven though, which is an asset particularly when dealing with shared business backends. It can take a while to get used to, but it does work and is an excellent way to sneak in implicit peer reviews. So code reuse is alive and well I think, what makes you think otherwise?
/Casper On Oct 13, 9:55 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > A couple of years ago the media was rife with all sorts of articles on > how the idea of code reuse was a simple way to improve productivity > and > code quality. > > From the blogs and sites I check on a regular basis it seems as though > the idea of "code reuse" has gone out of fashion. Perhaps the 'code > reuse' advocates have all joined the SOA crowed instead? :-) > > Interestingly enough, when you search for 'code reuse' in Google the > second result is titled: > > "Internal Code Reuse Considered Dangerous"! > > To me the idea of code reuse is just common sense, after all look at > the success of the apache commons project! > > What I want to know is: > > - Do you or your company try and reuse code? > - If so how and at what level, i.e. low level api, components or > shared business logic?How do you or your company reuse code? > - Does it work? > > Discuss? > > Karl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
