Evaluate the developer's
Performance)It is difficult to find a suitable anecdotal evital metric without relying on evidence. So we were very excited when we saw the rebel lab developer productivity research report-download link. This 40-page report examines the tools and practices that developers use in their daily lives. To enable the report to grasp the subject of "performance", rebel labs weighted the effects of different practices and tools on the predictability of software quality and version release.
The following are some practices used for measurement in the study report:
- Processing of technical debt (technical debt)
- Monitor and fix code Quality Problems
- Automated Testing
- Pair Programming
- Code Review
Implementing the above practices can improve the software quality, but what is the money and time cost? In this case, we need to use a predictable measure. Comparing these practices with the possibility of timely release of software, we can properly produce reliable measurements to check whether the time spent on improving quality can meet the deadline.
Handle technical debt
Technical debt refers to work delayed for other tasks. Most delayed tasks do not need to be processed immediately. However, if these tasks are not handled properly, they may cause more difficult problems in the future.
Conclusion: technical debt needs to be handled occasionally. It is not significant to solve the technical debt.
Solve the impact of technical debt on predictability and quality:
Monitor and fix code Quality Problems
Conclusion: Fixing code quality can significantly improve the quality of software and the predictability of release, probably because this practice will let engineers pay attention to potential structural problems in software applications.
Fixed the impact of code Quality Problems on predictability and quality:
Automated Testing
Conclusion: 100% using automated testing is better than partially testing coverage, but not using automated testing is slightly better than partially automated testing-probably because these engineers are manually testing their code.
Impact of automated functional testing on predictability and quality:
Pair Programming
Conclusion: Pair Programming (one person reviews the code and the other person writes the Code) has a significant impact on the software quality.
Impact of Pair Programming on quality and predictability:
Code Review
Conclusion: From the report, the review code has a significant impact on the predictability of software release, but has little impact on quality. This practice may help developers discover major design and orientation problems, but it does not expose small problems, such as software defects (bugs ).
Impact of code review on quality and predictability:
Address: https://medium.com/building-bowery/the-state-of-developer-productivity-e5a006f7b724
In-depth analysis of developers' productivity status
