Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!ico!vail!rcd
From: rcd@ico.isc.com (Dick Dunn)
Newsgroups: comp.software-eng
Subject: discarding prototypes
Summary: do it as a matter of principle!
Message-ID: <1989Oct19.021306.7336@ico.isc.com>
Date: 19 Oct 89 02:13:06 GMT
References: <1142@svx.SV.DG.COM> <34399@regenmeister.uucp> <5296@eos.UUCP> <14081@well.UUCP>
Organization: Interactive Systems Corporation
Lines: 43

In article <14081@well.UUCP>, shf@well.UUCP (Stuart H. Ferguson) writes:
> +-- bill@pd1.ccd.harris.com (Bill Davis) writes:
> | In article <> ejp@abvax.icd.ab.com (Ed Prochak) writes:
> | >Prototypes have to be treated as throw-aways,
> | >especially when they work!
> | 
> | I agree with throwing away prototypes when appropriate.
> | But, what makes a prototype something that should be
> | thrown away if it is working and providing useful
> | functions?...

It's not necessarily the characteristics of the prototype itself so much as
a "matter of principle" (a phrase which often suggests "no good reason":-)
to protect the process of prototyping.

If you want to be able to use prototyping, you have to know that when you
create a prototype, it's going to be just that.  Even if it does its job
well, it may not have the sort of internal characteristics that will let it
survive maintenance and adaptation.  Even if it has those as well, you
have to spend some time checking it over from the criteria of production
programs.

That's why I'd say throw it out as a matter of principle.  EVERY prototype
should get tossed.  (Then you can sneak in when nobody's looking and
scavenge the pieces you can use in the real thing...:-)

By protecting the process of prototyping, I intend first that NOBODY
outside the team responsible for implementing the "real" software should
ever even begin to ponder the possibility of hinting at broaching the
suggestion of considering turning the prototype into production code--
that allows the prototyping process to be corrupted from outside.  Nor
should the implementation team itself consider using the prototype, because
that may allow the idea of prototype->production to take root.  They may
also delude themselves into thinking they can use something they really
shouldn't.

However, since I never ever make ironclad rules, I'll admit that there is a
remote possibility that occasionally some significant piece of a prototype
can be used in production.  If you do it, don't blab it around, OK?  It'll
come back to haunt you.
-- 
Dick Dunn     rcd@ico.isc.com    uucp: {ncar,nbires}!ico!rcd     (303)449-2870
   ...No DOS.  UNIX.