2 ms·
I think it's not so much unintended consequences as it is perverse incentives. It's the same as measuring a programmers output by Lines of Code, you're just go
by toomanybeersies 8y ago
I think it's not so much unintended consequences as it is perverse incentives.
It's the same as measuring a programmers output by Lines of Code, you're just going to get a heaping mass of code that could be done in 1/10th of the lines.
- dfsgh 8y agoagreed I worked as a consultant for a company that had exactly that problem. They based promotions based on lines of working code. Result: You would see huge bloobs of autogenerated code getting shipped that could have been done with about 5% of that code, and then later get discarded by security as a security risk. Even after my consulting(I was hired to fine our how mouch of there code is rly a security risk like there industry partners claim) they did not change there practice for 3 Years. Im surprised the Company even survived, but it did and after 3 Years a big restructering basicly fired all of IT management.