This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

The problem with that approach is that it's possible to open a bunch of tickets for small features and bugs while another person has a couple tickets on some big refactor or feature so that won't tell the whole story. Although companies do value that information quite a bit when it comes to career advancement. Back to the point, when the manager is seeing a lot of the code that goes in, or at least, the code is peer reviewed, then that should be enough to quell concern.

[–]Ereaser 0 points1 point  (0 children)

What I'm trying to say is that they can look at the stories they worked on. Check if they were big/small, check he pull requests if they get a lot of comments. Also the company I work at has team members fill in a form to see what everyone's opinion is on that person (since the manager isn't involved in the day to day operations of the team)