3 ms·

If you use "number of lines of code" as a metric for productivity, soon people will double-space their code. We went through that in the 90s.

• khazhou 9y ago
  Were there any other signs you had shitty programmers on your team?
  • ktRolster 9y ago
    It's not about shitty or good, it's about management. Whatever you reward, that's what people will give you. See also: https://users.cs.duke.edu/~ola/courses/cps108/code/java/harpoon/images/dilbert/bug.gif https://users.cs.duke.edu/~ola/courses/cps108/code/java/harp...
    • Osmose 9y ago
      You're arguing against an extreme, though. Sure, if LOC added (or even just changed, which is the saner metric) was linked directly to bonuses, it'd be ripe for abuse. But that completely ignores the more reasonable use in the article, as one (of several) metrics used to measure the impact of their release process.
      • deleted 9y ago
        [deleted]
      • ktRolster 9y ago
        You should measure what you want more of. Unless for some reason you want more lines of code, then use a different metric.
      • gardnr 9y ago
        They should measure and reward lines of code removed instead.
  • testvox 9y ago
    Measuring productivity in LOC...