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=3.4 required=5.0 tests=BAYES_50,INVALID_DATE, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Xref: utzoo comp.object:2745 comp.lang.ada:4978 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!ogicse!milton!hayes.ims.alaska.edu!acad3.alaska.edu!ftpam1 From: ftpam1@acad3.alaska.edu (MUNTS PHILLIP A) Newsgroups: comp.object,comp.lang.ada Subject: Re: ada-c++ productivity Keywords: Looking for a few lazy men Message-ID: <1991Mar17.083823.9272@ims.alaska.edu> Date: 17 Mar 91 08:38:23 GMT References: <11966@pasteur.Berkeley.EDU> <1991Mar15.224626.27077@aero.org> <1991Mar16.205228.4268@grebyn.com> Sender: usenet@ims.alaska.edu (J Random USENET) Reply-To: ftpam1@acad3.alaska.edu Organization: University of Alaska Fairbanks News-Software: VAX/VMS VNEWS 1.3-4 Nntp-Posting-Host: acad3.alaska.edu List-Id: In article <1991Mar16.205228.4268@grebyn.com>, ted@grebyn.com (Ted Holden) writes... >Productivity of C++ users will vary according to skills, experience >levels, tools available, such as the fabulous new Borland interface, and >the task at hand. An idea of productivity in Ada projects may be had >from the Feb. 11 issue of Federal Computer Week: .. > "Three lines of code per day is absurd [as if ten wasn't], said > Ralph Crafts, editor of a newsletter on Ada, and an expert > witness for the protester..... > >Whether any realistic combination of events exists which could reduce >Pascal, C, or C++ programmers to this level of productivity is anybody's >guess; my own opinion is that most C programmers would require a bullet >through the brain to be brought to such a level. .. Actually, 10 lines per day isn't all that unreasonable, averaged over a year for example. The keyword is AVERAGED: on a good day I may write hundreds of lines of code; I may spend the next day trying to find an obscure bug in one of those lines. A programmer also does a lot of other things like attending meetings, reading documentation, writing documentation, studying a problem, answering the phone, filling out forms, reformatting that [censored] hard disk, etc. Then there is waiting for the network to come back up, putting paper in the laser printer... In theory, you are supposed to spend most of your time DESIGNING rather than CODING, as well. I have spent days perfecting algorithms that were set down in code in hours or even minutes. In the ideal case, the manager would chain his slaves, er, employees to their computer until the job is done. In practice things don't work out that way. The whole idea of "lines per day" is pretty artificial anyway. (The contract says x lines per day so we'll just pad things out with a little whitespace...) What matters is whether a product is delivered on time or not, and if it meets the spec. CAVEAT: Most of what I do is in assembly language or Turbo Pascal. I don't particularly like C or C++ (or assembly language for that matter) and I haven't found an Ada compiler that generates decent code. (I am constrained to the low end of the marketplace, being self- rather than government-employed.) Philip Munts N7AHL NRA Extremist, etc. University of Alaska, Fairbanks