|
|
|
|
|
by kotlin2
1332 days ago
|
|
I think LoC has been determined to be a bad productivity metric because it’s gameable and incentivizes bad behavior. However, that doesn’t apply here as the engineers didn’t know they were going to be evaluated by LoC a priori. I struggle to think of cases were lines-changed wouldn’t be correlated with the productivity of engineers working in a consistent environment if they weren’t trying to game the system. |
|
And sure, if I was getting judged by LoC I'd just paste in a library versus including it, which would generally be worse.