Flight planning spreadsheet

"G.R. Patterson III" wrote in message
...


Roger Halstead wrote:

OTOH you will
never get some programmers to use structured programming with pretty
printing and internal documentation.

We used 100% code reviews by "peers" at my former employer. Those who
didn't
use structured programming didn't stay long.

Then again, that extra time may grate on management. When they see a
programmer write code in a day that takes another two or three, they
see efficiency.

I've seen plenty of C programmers crank out 30KLOC of garbage that had to be
throw away.


Since my former employer was not in the habit of handing the same
assignment
to several programmers, this never happened. Number of lines of code was
not a factor in evaluation; what mattered was whether you had completed
assignments on time, the perceived complexity of those assignments, and
the number of bugs turned up in testing.

Unfortunately for the IT field, KLOCs typically WERE the main point for
evaluation, particualrly by non-technical magagement.

Both the number of lines of code
*and* the number of comment lines *were* recorded, however.

Sad to say, non-objective measures have become the bean-counters standard
for measurement.