{'fraction_non_alphanumeric': 0.015765765765765764, 'fraction_numerical': 0.0022522522522522522, 'mean_word_length': 5.13103448275862, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Metrics to quantify software developer experience: a systematic mapping

The quality of the developers has a direct impact on the software product. Besides the code they write, an experienced developer may define architectural solutions essential to the system's maintainability. This condition is necessary to develop new features and fix defects in a timely and cost-effective manner. Some works have studied the impact of developer experience and use metrics to study the relationship with the maintainability and evolution of software. In this systematic mapping, we present a catalog of metrics that have been used to quantify developers' experience, found in 34 works. These metrics are classified by the type of experience they represent and the purpose of using them. The results showed that most of the selected studies use metrics based on counting developer activities in code.