Comments or Issues: Where to Document Technical Debt?
<|reference_start|>Comments or Issues: Where to Document Technical Debt?: Self-Admitted Technical Debt (SATD) is a form of Technical Debt where developers document the debt using source code comments (SATD-C) or issues (SATD-I). However, it is still unclear the circumstances that drive developers to choose one or another. In this paper, we survey authors of both types of debts using a large-scale dataset containing 74K SATD-C and 20K SATD-I instances, extracted from 190 GitHub projects. As a result, we provide 13 guidelines to support developers to decide when to use comments or issues to report Technical Debt.<|reference_end|>
@article{xavier2024comments,
    title={Comments or Issues: Where to Document Technical Debt?},
    author={Laerte Xavier and Jo~ao Eduardo Montandon and Marco Tulio Valente},
    journal={IEEE Software 39.5 (2022)},
    year={2024},
    doi={10.1109/MS.2022.3170825},
    archivePrefix={arXiv},
    eprint={2408.15109},
    primaryClass={cs.SE}
}