4 ms·
I don't think it rises even to 40%, because I think an excessively productive idiot is way harder to deal with than a person who just doesn't write enough code.
by PuppyTailWags 4y ago
I don't think it rises even to 40%, because I think an excessively productive idiot is way harder to deal with than a person who just doesn't write enough code. Cutting based on LOC biases towards retaining excessively productive idiots.
- paxys 4y agoAn engineer who writes a lot of code and contributes nothing of value is an outlier. An engineer who writes no code but contributes a lot of value is an outlier. So yes, you will miss these two outliers if you go by LoC, but sometimes that is acceptable as long as you are handling the majority correctly.
- PuppyTailWags 4y agoThe thing is, in my experience, the people who write a ton of LoC often need more effort to review, introduce instability, and slow down the rest of their team because their stuff needs bugfixing or is difficult to parse.
- paxys 4y agoThere's an easy way to validate these assumptions. Go to any repo in your company's GitHub and open the contributors section. Tell me who you'd rather fire - the 10 people on the top of the page or the 10 people at the bottom?
- newaccount74 4y agoWell, it's apparently a good way to get rid of the accessibility team. Who needs those folks?
- paxys 4y agoSome teams (accessibility, diversity & inclusion) were fired because Elon doesn't give a shit about those areas. That has nothing to do with lines of code.
- watwut 4y agoThe 10 people in the bottom are people whose primary job is not to code. I don't actually want to fire my team leader nor the guy who often helps analysts, I actually think they do good job.