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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,41100a78496a4c71 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-04 18:27:27 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!colt.net!newspeer.clara.net!news.clara.net!peer.news.zetnet.net!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Nethack! (was): AdaGames Date: Thu, 4 Apr 2002 11:48:53 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: References: <98104da8.0203280310.143a1c18@posting.google.com> <4519e058.0203290613.73b55af4@posting.google.com> <6g4gaugv9a85i56kvgcgmu4h2jkjprutec@4ax.com> <4519e058.0204010704.ed2cd06@posting.google.com> <4519e058.0204021030.14127b06@posting.google.com> <4519e058.0204030750.78a30287@posting.google.com> <3CAC7AC6.A6DBDC32@despammed.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1017938935 626 136.170.200.133 (4 Apr 2002 16:48:55 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 4 Apr 2002 16:48:55 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:22127 Date: 2002-04-04T16:48:55+00:00 List-Id: Its hard to collect metrics without having at least *some* of the developers feeling that they will be rewarded or punished on the basis of the data you collect. Hence, there's always *some* incentive to cheat. However, at least in the studies I was involved in, there was a lot of grumbling about metrics, but I never saw any obvious attempts to inflate or otherwise doctor the measurements of code size. Whatever you use: SLOCs, Semicolons, Halstead Bits, Source Bytes, Object Bytes, anything. They all have weaknesses & can be artificially controlled. But what choices do we have? We need some means of at least roughly approximating code size or we might as well give up on trying to measure & understand what we do. (I've been told by just about all of the developers I ever collected metrics from that this would be just fine with them. However after years of doing it, we were definitely able to see improvements in our processes.) MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com "Wes Groleau" wrote in message news:3CAC7AC6.A6DBDC32@despammed.com... > > This is true as long as the programmers were not > thinking that there would be any reward or punishment > for a higher or lower count. Take a well-written > module of a reasonable size in any language, and there > are usually ways to greatly change the metric without > changing behavior. >