Unfortunately for larger games individual devs don’t have that much control nor can have a mensurable impact. For example, I wrote a few lines of code for a large game, those lines will be executed every single time the game runs, but if they weren’t there no user would notice. I was told to write those lines, and it’s not something I personally wanted to add to the game, there was an issue, I was sent to fix it, I did. This is true for the vast majority of the game code, most devs are pointed to issues to fix or features to implement, they have some wiggle room in the how to do stuff, but the what to do has been approved by the boss of the manager of your manager’s manager, and unless there’s a good reason it won’t change.
Think about it this way, have you ever watched the credits from a AAA game? The vast majority (as in there are likely only a couple of persons who didn’t) of the people in that list contributed something to the game, either directly or indirectly, it’s hard to measure how much each contributed, a small but critical fix might be more important than a large but unused feature, how do you measure between the two?. Not to mention past employees who did stuff for a previous game that got re-used.
Don’t get me wrong, it’s a nice idea, one that I would personally benefit from, but I think it’s just not feasible for large games. In short it’s impossible to be fair doing that, and people would get hurt because John from accounting got the same share that he did. And if you do it in any other way that’s not everyone gets the same share, you’re essentially playing favorites with the people whose job is to do the stuff you’ve ranked higher, even though the other person’s job is just as important.
Unfortunately for larger games individual devs don’t have that much control nor can have a mensurable impact. For example, I wrote a few lines of code for a large game, those lines will be executed every single time the game runs, but if they weren’t there no user would notice. I was told to write those lines, and it’s not something I personally wanted to add to the game, there was an issue, I was sent to fix it, I did. This is true for the vast majority of the game code, most devs are pointed to issues to fix or features to implement, they have some wiggle room in the how to do stuff, but the what to do has been approved by the boss of the manager of your manager’s manager, and unless there’s a good reason it won’t change.
Think about it this way, have you ever watched the credits from a AAA game? The vast majority (as in there are likely only a couple of persons who didn’t) of the people in that list contributed something to the game, either directly or indirectly, it’s hard to measure how much each contributed, a small but critical fix might be more important than a large but unused feature, how do you measure between the two?. Not to mention past employees who did stuff for a previous game that got re-used.
Don’t get me wrong, it’s a nice idea, one that I would personally benefit from, but I think it’s just not feasible for large games. In short it’s impossible to be fair doing that, and people would get hurt because John from accounting got the same share that he did. And if you do it in any other way that’s not everyone gets the same share, you’re essentially playing favorites with the people whose job is to do the stuff you’ve ranked higher, even though the other person’s job is just as important.
exactly - it is borderline impossible to manage on large scale projects with any semblance of coherence.