All this reminds me of the whole
on mappers versus packers (partucularly in Chapter 1).
It's difficult for non-software-development people to
understand the process of development -- to them, it
sometimes looks like we're just goofing off and if they
were just able to get us to apply ourselves we'd be that
much more productive.
One of the problems is that code isn't an easy
product to create metrics for. Sure, there's quantity, and
sure, there's output (does it do what it's supposed to?),
but I think non-development people always have the
suspicion that it could always do more and that it's the
lazy developer's fault it doesn't.