English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Zendy Plus

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Zendy Tools

Zendy Open

Technical Debt (TD) refers to the situation where developers make trade-offsto achieve short-term goals at the expense of long-term code quality, which canhave a negative impact on the quality of software systems. In the context ofcode review, such sub-optimal implementations have chances to be timelyresolved during the review process before the code is merged. Therefore, wecould consider them as Potential Technical Debt (PTD) since PTD will evolveinto TD when it is injected into software systems without being resolved. Todate, little is known about the extent to which PTD is identified in codereviews. To this end, we conducted an exploratory study in an attempt tounderstand the nature of PTD in code reviews and track down the resolution ofPTD after being identified. We randomly collected 2,030 review comments fromthe Nova project of OpenStack and the Qt Base project of Qt. We then manuallychecked these review comments, and obtained 163 PTD-related review comments forfurther analysis. Our results show that: (1) PTD can be identified in codereviews but is not prevalent. (2) Design, defect, documentation, requirement,test, and code PTD are identified in code reviews, in which code anddocumentation PTD are the dominant. (3) 81.0% of the PTD identified in codereviews has been resolved by developers, and 78.0% of the resolved TD wasresolved by developers within a week. (4) Code refactoring is the main practiceused by developers to resolve the PTD identified in code reviews. Our findingsindicate that: (1) review-based detection of PTD is seen as one of thetrustworthy mechanisms in development, and (2) there is still a significantproportion of PTD (19.0%) remaining unresolved when injected into the softwaresystems. Practitioners and researchers should establish effective strategies tomanage and resolve PTD in development.

Potential Technical Debt and Its Resolution in Code Reviews: An Exploratory Study of the OpenStack and Qt Communities