× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: programmer productivity.
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Fri, 10 Nov 2000 14:19:37 -0800
  • Organization: Pacer International

Well, when I write a program I do a LOT of edit/compiles, because of the way
I program.  Such as if I'm writing a program that's going to be changing data
enmasse I'll first write it as a report showing me all the records it's 
selecting, and the values it determines to change.  Then when I know that is
100% correct, I'll change the program to actually change the data.  Then I'll
run it on test data, then run it on live data.

Also, I write programs in a modular fashion.  I'll write sections of programs
and compile them and test them to make sure they work, then add new modules,
etc...  Depends on how big the program is though.

So, since I do all these edits and compiles I'll less productive then a 
programmer
who just compiles once?

Well, we have a consultant we USED to use.  He would come in, bang out a 
program,
compile it and leave.  Very productive, eh?  Except that the programs NEVER 
worked.
Not once was a program working when he left.  I would have to debug it my self, 
or
wait forever and a day to get him back here to fix it.  But hey, one edit, one 
compile.

I think the biggest thing we need to look at is, does the program work as 
advertised?
If programmer A spends longer to write a program than programmer B, but 
programer A's
program is bug free and programmer B's program is riddled with bugs, who's more
productive?  I don't think there's anyone here who would say programmer B.

Regards,

Jim Langston

Date: Fri, 10 Nov 2000 13:57:37 -0500
From: Buck Calabro <buck.calabro@aptissoftware.com>
Subject: RE: programmer productivity.

Brad Stone wrote:

<SNIP>

A more interesting
measurement is number of edit/compile cycles to complete the project.  Sort
of makes you think before compiling.  And isn't it the thinking part we want
to reward?

<SNIP>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.