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: nabbasi@earthlink.net Subject: Re: Distinguishing type names from other identifiers Date: 1998/01/17 Message-ID: <69rnvv$gjr@drn.zippo.com>#1/1 X-Deja-AN: 316981193 References: <884736089.2104295427@dejanews.com> <69lael$90o@top.mitre.org> <01bd2207$18f3fac0$95fc82c1@xhv46.dial.pipex.com> <69nt40$q7n@top.mitre.org> Organization: Original Zippo News Service [http://www.zippo.com] Newsgroups: comp.lang.ada Date: 1998-01-17T00:00:00+00:00 List-Id: > >On 16 Jan 1998, Robert Dewar wrote: >> >> On the other hand, uniformity of syntax is NOT about reducing bugs. It is >> about creating a code base that everyone in the group feels comfortable >> with, so that you avoid the phenomenon, all too common I am afraid in many >> large projects, of individuals "owning" pieces of the code and (a) not >> wanting anyone else to mess with their parts and (b) not being willing to >> mess with other peoples code. I view the idea of a programmer owning a particulare part of the software (say a subsystem, or a number of packages or a number of clases etc..) as more of having personal responsibility for what they are working on, NOT as being not wanting others to touch their code or they not wanting to touch someone else code. This is why I don't agree that each programmer should not "own" what they are working on. again, owning here means to me that they are "responsible" for that they are working on, it is a positive thing, not a negative one. Otherwise, it becomes programming by committe, no one is responsible for any thing going wrong, becuase no one owns the code. If one part of the software is not working, one can't hold any person responsible, this seems to me to allow lazy and bad programmers to ride on the shoulder of better programmers. The best situation is where programmers are held responsible for what they write, to be held responsible for what you write must imply ownsership of the code, but at the same time, having the code such that any one can easily read each other's code or even modify each other code if the need arises. I beleive in having common style and common standards, but at the same time, owning what you write. just my 1.88 cents offcourse. thanks, Nasser