From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,2afac1a4161c7f35
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: who owns the code? was Re: Distinguishing type names from other
 identifiers
Date: 1998/02/03
Message-ID: <dewar.886561410@merv>#1/1
X-Deja-AN: 321872436
References: <En96zv.9LA@world.std.com>
 <19980203214601.QAA12150@ladder03.news.aol.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 886561683 31100 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-02-03T00:00:00+00:00
List-Id: <comp.lang.ada>


Todd says

<<So do I, although it is at some times a very hard personal internal battle when
it comes to having someone else find faults or bad assumptions in the code I've
created.  However, once all is laid out on the table I learn from it and try to
avoid the same mistakes.  I also never blame the individual who found the
fault, in fact I let them know that I appreciate their insight.
>>

for me, things are quite different. If I make a stupid or not-so-stupid
error in my code, and someone else finds it (and preferably fixes it),
my only reaction is to thank that person for helping to improve the
code -- basically the point is that it is *not* an error in *my* code
at all, it is an error in *our* code, and it is completely irrelevant
who put it there, what is important is for *us* to fix it.

Robert

Note: I realize that to achieve this requires a group of people all of
whom are self-confident, and respect one anothers work. But that's a good
goal anyway for any group effort.