4 ms·
It is difficult to accurately evaluate software engineer productivity. I don’t question there are developers who get by doing absolutely nothing. However, only
by cebert 2y ago
It is difficult to accurately evaluate software engineer productivity. I don’t question there are developers who get by doing absolutely nothing. However, only analyzing git commits doesn’t consider other aspects of software engineering such as producing design docs, code reviews, planning, support, etc. If you try to evaluate the performance of individuals just based on git commits alone, you risk making terrible decisions.
- blackeyeblitzar 2y agoYes but it’s not like those producing code don’t do those other things. You would expect typical commits to reflect the time lost to other typical activities right?
- cebert 2y agoMaybe you’ve worked on better teams than I have. There are some folks who only care about their feature and getting their JIRA item across the board vs the quality of the product they are building and the overall health of the team. Some of these types may have more commits, but they’re not always great team players or great people to work with. Metrics might suggest these engineers are the most valuable and productive, but in reality, they can be a significant drain on teams and projects. They don’t actively participate in code reviews, show little concern for performance and code quality, and rarely contribute to support efforts or keeping dependencies current. Their lack of collaboration and accountability makes them challenging teammates and ultimately hinders the team’s success. There’s more to being a good software engineer and teammate than the number of and size of commits.