Xref: utzoo comp.object:3087 comp.software-eng:5295
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!transfer!lectroid!jjmhome!smds!rh
From: rh@smds.UUCP (Richard Harter)
Newsgroups: comp.object,comp.software-eng
Subject: Re: How to pay for reusable software
Summary: Good programmers reuse their own code
Message-ID: <387@smds.UUCP>
Date: 9 Apr 91 04:50:06 GMT
References: <1991Apr3.231849.13410@m.cs.uiuc.edu> <3318:Apr705:51:2391@kramden.acf.nyu.edu>
Followup-To: comp.software-eng
Organization: SMDS Inc., Concord, MA
Lines: 19

In article <1991Apr3.231849.13410@m.cs.uiuc.edu> johnson@cs.uiuc.EDU (Ralph Johnson) writes:
> This leads to an interesting problem: how can we afford to pay the
> costs of developing reusable software?

There have been some studies that show that one of advantages of
the more productive programmers is that they reuse their own code.
When one thinks about it, this is the optimal situation for reusability.
I.e. the programmer is already familiar with the way the code works,
its style, and its limitations.  Furthermore she/he knows that the code
exists and where to find it.  Moreover "resusable code" in this context
often consists of sections of code rather than complete modules.  It
might be profitable to think in terms of bridging the gap between
programmers so that programmer X can reuse the code of programmer Y
in much the same way that a programmer reuses her own code.
-- 
Richard Harter, Software Maintenance and Development Systems, Inc.
Net address: jjmhome!smds!rh Phone: 508-369-7398 
US Mail: SMDS Inc., PO Box 555, Concord MA 01742
This sentence no verb.  This sentence short.  This signature done.