For code contributors, there’s metrics involved now. Even within tiers of needs improvement, meets, or exceeds, they have top, middle, and low rankings. Basically tracking commits from forked branches of mainstream repos. I’m sure they used this as part of the layoff decisions.
8 replies (most recent on top)
AI replacements incoming
Well, obviously one needs to commit a bug, then commit a bug fix. Double bonus. After all, "the world needs ditch diggers".
@OP I remember that OT guy talking about that few years+ back.
@a7 In Teams go to PowerBI and look for something called "Engineer Report". Maybe it's only visible to ProdOps, I don't know.
I was in the top 5 in the code commits in a 20 member team in the org, yet I was laid off.
You can be laid off for any reason.
@a5 where can we find it?
There's public PowerBI report that you can look at. It has code contribution, jira stories closed, etc metrics for every employee.
IMO, this is a terrible way to track developer productivity. There needs to be more nuance. Like how many of your commits make it into production? What about investigate bug work that takes time but involves small code changes. Or being a driver to get something done/fixed but requires other teams to do the actual changes.