3 ms·
It appears to make sense. It doesn't necessarily make sense, because it assumes you're accurately able to gauge productivity. This implies you have some reliab
by TheOtherHobbes 8y ago
It appears to make sense. It doesn't necessarily make sense, because it assumes you're accurately able to gauge productivity.
This implies you have some reliable and realistic metrics for code quality, and/or that all workers in a team are functionally identical.
Neither are likely to be true in practice. This doesn't mean older = better, or older = worse, or older = identical. It means you need to assess the value of individuals in a team individually.
Otherwise you're just doing scorched earth HR, with predictable consequences.
- mirimir 8y agoI agree. I wasn't arguing for the validity of those approaches. Just that they could account for older workers being fired disproportionately, with no "intentional" age discrimination. Which isn't to say that HR doesn't realize that their approach targets older workers. Just that they can say that it wasn't intentional.