Self-Admitted Technical Debt (SATD) are comments, left by developers in the source code or elsewhere, aimed at describing the presence of TD, i.e., source code "not ready yet''. Although this was never stated in the original paper by Potdar and Shihab, the term SATD might suggest that it refers to a ``self-admission'' by whoever has written or changed the source code. This paper empirically investigates, using a curated SATD dataset from five Java open source projects, (i) the extent to which SATD comments are introduced by authors different from those who have done last changes to the related source code, and (ii) when this happens, what is the level of ownership those developers have about the commented source code. Results of the study i...
Technical debt refers to taking shortcuts to achieve short-term goals, which might negatively influe...
Technical Debt is a metaphor used to describe the situation in which long-term software artifact qua...
Self-Admitted Technical Debt (SATD) represents the admission, made through source code comments or o...
Self-Admitted Technical Debt (SATD) are comments, left by developers in the source code or elsewhere...
Technical Debt (TD) has been defined as "code being not quite right yet", and its presence is often ...
Technical Debt (TD) has been defined as "code being not quite right yet", and its presence is often ...
Self-admitted technical debt (SATD) consists of annotations, left by developers as comments in the s...
Technical debt refers to the phenomena of taking shortcuts to achieve short term gain at the cost of...
Self-Admitted Technical Debt (SATD) is a particular case of Technical Debt (TD) in which developers ...
Technical debt denotes shortcuts taken during software development, mostly for the sake of expedienc...
Technical debt denotes shortcuts taken during software development, mostly for the sake of expedienc...
Self-Admitted Technical Debt (SATD) is a form of Technical Debt where developers document the debt u...
Technical debt refers to taking shortcuts to achieve short-term goals, which might negatively influe...
Technical Debt is a metaphor used to describe the situation in which long-term software artifact qua...
Self-Admitted Technical Debt (SATD) represents the admission, made through source code comments or o...
Self-Admitted Technical Debt (SATD) are comments, left by developers in the source code or elsewhere...
Technical Debt (TD) has been defined as "code being not quite right yet", and its presence is often ...
Technical Debt (TD) has been defined as "code being not quite right yet", and its presence is often ...
Self-admitted technical debt (SATD) consists of annotations, left by developers as comments in the s...
Technical debt refers to the phenomena of taking shortcuts to achieve short term gain at the cost of...
Self-Admitted Technical Debt (SATD) is a particular case of Technical Debt (TD) in which developers ...
Technical debt denotes shortcuts taken during software development, mostly for the sake of expedienc...
Technical debt denotes shortcuts taken during software development, mostly for the sake of expedienc...
Self-Admitted Technical Debt (SATD) is a form of Technical Debt where developers document the debt u...
Technical debt refers to taking shortcuts to achieve short-term goals, which might negatively influe...
Technical Debt is a metaphor used to describe the situation in which long-term software artifact qua...
Self-Admitted Technical Debt (SATD) represents the admission, made through source code comments or o...