How long do junior developers take to remove technical debt items?
Lenarduzzi, Valentina; Mandić, Vladimir; Katin, Andrej; Taibi, Davide (2020-10-05)
Lenarduzzi, Valentina
Mandić, Vladimir
Katin, Andrej
Taibi, Davide
05.10.2020
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:tuni-202103112523
https://urn.fi/URN:NBN:fi:tuni-202103112523
Kuvaus
Peer reviewed
Tiivistelmä
<p>Background. Software engineering is one of the engineering fields with the highest inflow of junior engineers. Tools that utilize source code analysis to provide feedback on internal software quality, i.e. Technical Debt (TD), are valuable to junior developers who can learn and improve their coding skills with minimal consultations with senior colleagues. Objective. We aim at understating which SonarQube TD items junior developers prioritize during the refactoring and how long they take to refactor them. Method. We designed a case study with replicated design and we conducted it with 185 junior developers in two countries, that developed 23 projects with different programming languages and architectures. Results. Junior developers focus homogeneously on different types of TD items. Moreover, they can refactor items in a fraction of the estimated time, never spending more than 50% of the time estimated by SonarQube. Conclusion. Junior Developers appreciate the usage of SonarQube and considered as a useful tool. Companies might ask junior developers to quickly clean their code.</p>
Kokoelmat
- TUNICRIS-julkaisut [20173]