In our software company, someone might write a new feature - but 2 other people were involved in designing it, someone else is going to write the database changes to support it, another person will update the documentation to tell users how to use it, someone else will test it to make sure it works - who gets "credit" for it? It's sort of irrelevant.
That doesn't mean we don't cheer individual engineers when they make us cool things or fix bugs - we have one engineer who is like Santa and gives us presents at our dev meetings - he shows us whatever new thing he is building - mostly to get feedback, but we cheer and get excited so he gets his positive reinforcement.
But at the end of the year, we don't have a tally book that says "this person wrote this many features and fixed this many bugs" - we just keep moving forward.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2022-04-05 09:10 pm (UTC)In our software company, someone might write a new feature - but 2 other people were involved in designing it, someone else is going to write the database changes to support it, another person will update the documentation to tell users how to use it, someone else will test it to make sure it works - who gets "credit" for it? It's sort of irrelevant.
That doesn't mean we don't cheer individual engineers when they make us cool things or fix bugs - we have one engineer who is like Santa and gives us presents at our dev meetings - he shows us whatever new thing he is building - mostly to get feedback, but we cheer and get excited so he gets his positive reinforcement.
But at the end of the year, we don't have a tally book that says "this person wrote this many features and fixed this many bugs" - we just keep moving forward.