Reply to thread

Message

[QUOTE="James Kanze, post: 3915933"]
Everything:-).

Seriously, it is a difficult question.  One of the reasons I
keep coming back to errors per KLOC is because it is easily
quantified and measured.  Most other aspects, many just as
important, aren't so easily quantified and measured.  In my
experience, code with few errors tends to be easier to maintain,
because the techniques used to reduce the errors also make code
more readable.  But I can't quantify that.  And customer
satisfaction is even vaguer, at least in some environments.
(I've worked on a number of systems were all that was required
was that the program work as specified.  24 hours a day, 7 days
a week, without interruption.  No crashes or incorrect behavior,
and the customer was satisfied.  But that's certainly not
sufficient for a lot of programs.)

How do you quantify the customer satisfaction?

Of course, there are many aspects to consider.  I think you're
an independent---in a very real sense, your code is "good" if it
brings you repeat business, and bad otherwise.  (But I think
you're professional enough to set your standards a bit higher
than just that.)
[/QUOTE]

Verification