I used to work for a company which measured LOC, and programmers would fluff out their routines with vast tables of parameters and limits and dependancies and interfaces... Hundreds and hundreds of lines for even the simplest routine. They cited "standardization" -- every routine would have the same documentation and would therefore be just as readable as any other.
Of course, this led to hundreds of one-line (litteraly) routines which simply stored a value or incremented a counter -- each having the required standardized header. These programmers generated MILLIONS of lines of code.
I say, "Bravo."
Needless to say, those millions of lines of code were unbelieveably bug ridden. In my project, I took 20K lines of this stuff, doubled the functionality, doubled the throughput, eliminated the known bug list, ported the system to two other machines, and ended up with 12K lines.
Slashdot Mirror
Of course, this led to hundreds of one-line (litteraly) routines which simply stored a value or incremented a counter -- each having the required standardized header. These programmers generated MILLIONS of lines of code.
I say, "Bravo."
Needless to say, those millions of lines of code were unbelieveably bug ridden. In my project, I took 20K lines of this stuff, doubled the functionality, doubled the throughput, eliminated the known bug list, ported the system to two other machines, and ended up with 12K lines.
I must be part of the problem...