From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: ** X-Spam-Status: No, score=2.1 required=3.0 tests=BAYES_50,FREEMAIL_FROM, FROM_STARTS_WITH_NUMS,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.5-pre1 Date: 26 Mar 91 00:43:49 EST From: Eric C Aker <71660.412@CompuServe.COM> Subject: LOC Lines of Code debate Message-ID: <"910326054349 71660.412 CHE55-1"@CompuServe.COM> List-Id: I just have to get in to this debate. When I was working for a major airplane company some years ago all of the programmers were told to give a LOC count in each weakly (sic) report. Of course a tool was written to automatically count lines and give differences from last week. We all grumbled and one of the programmers came up with this great analogy. "Measuring progress on a SW project in lines of code is like measuring progress on an airplane in pounds of aircraft designed. Would any serious manager ask his aircraft designers how many pounds of airplane did you design this week? It is true that after the aircraft is done you can compute productivity in pounds of aircraft per manday, but it is not a very useful number."