Fatuous Measures of Code Size
Beloved of IBM managers, KLOCs (thousands of line of code) are possibly one of
the most pointless way of measuring programs ever devised. But how to explain
to people without any software background at all (in this case, architects and
designers who make up the greater part of the cross-discipline project I'm
currently working on) the magnitude of a programming task when it appears on
the task list as but a single deliverable? What if we were to print out the
source code in the format of a novel? One of my slides for the quarterly
review meeting tomorrow now contains the following:
Wonder if that'll impress them? I'm certainly alarmed as to how big it's become...
(Tesseræ is the dynamic component compiler system that's formed the bulk of my work here at Imperial for the last few years.)
Wonder if that'll impress them? I'm certainly alarmed as to how big it's become...
(Tesseræ is the dynamic component compiler system that's formed the bulk of my work here at Imperial for the last few years.)