3 ms·
surely this assessment introduces false positives? Someone that implements a poorly specified feature exceptionally well suffers rework, not because their code
by Quarrelsome 10y ago
surely this assessment introduces false positives? Someone that implements a poorly specified feature exceptionally well suffers rework, not because their code is poor but due to outside factors. Someone who cherry picks easy items is reflected as prolific where a perfectionist might just be given more difficult problems.
Idk, I worry that people will interpret this backwards and rather than having characteristics of a good developer ape those characteristics to appear as a good developer.
- nine_k 10y agoWhatever you measure, when people know it, will affect how people act. People will try to move the needle in the direction they see profitable, even unconsciously.
- Bartweiss 10y agoI think Goodhart's Law is in effect here. As a management metric, I would find this concerning - perverse incentives and false positives all over the place. But as a personal observation, I'm going to take it to heart. This (like most other metrics) seems most useful from a starting point of "while doing my daily work and seeking to write good code, I will apply this". That doesn't make a good tool for deciding who's talented, but I'm still going to remember it.