|
|
|
|
|
|
by password11
1220 days ago
|
|
|
>> 3. It encourages a ton of code churn with very low signal. > 3) “Code churn” is a very uncharitable description of day-to-day maintenance of an active codebase. Also implicit in the discussion is the fact that Google and other big tech companies performance review based on "impact" rather than arbitrary metrics like "number of PRs/LOCs per month". This provides a check on spending too much engineer time on maintenance PRs, since they have no (or very little) impact on your performance rating. |
|
|
Umm, from whatever I have seen in big tech "impact" is also fairly arbitrary. It all is based on how cozy one is with one's manager, skip manager, and so on. More accurate is "perception of impact".
Especially as it gets more and more nebulous at higher levels.