Quantifying and characterizing clones of self-admitted technical debt in build systems
Self-Admitted Technical Debt (SATD) annotates development decisions that intentionally exchange long-term software artifact quality for short-term goals. Recent work explores the existence of SATD clones (duplicate or near duplicate SATD comments) in source code.
Tao Xiao 0001 +5 more
openaire +2 more sources
SATDAUG - A Balanced and Augmented Dataset for Detecting Self-Admitted Technical Debt
Self-admitted technical debt (SATD) refers to a form of technical debt in which developers explicitly acknowledge and document the existence of technical shortcuts, workarounds, or temporary solutions within the codebase. Over recent years, researchers have manually labeled datasets derived from various software development artifacts: source code ...
Edi Sutoyo, Andrea Capiluppi
openaire +3 more sources
Towards the Repayment of Self-Admitted Technical Debt [PDF]
Technical Debt is a metaphor used to express sub-optimal source code implementations that are introduced for short-term benefits that often must be paid back later, at an increased cost.
Sierra, Giancarlo
core
Source code quality in connection to self-admitted technical debt
The importance of software code quality is increasing rapidly. With more code being written every day, its maintenance and support are becoming harder and more expensive. New automatic code review tools are developed to reach quality goals.
Hrynko, Alina
core +1 more source
An empirical study on discovering a new self-admitted technical debt type - API-debt
Self-Admitted Technical Debt (SATD) is when developers intentionally choose to take short-cuts, non-optimal solutions (e.g. temporary fix or rush code development) that negatively contribute to long-term source-code quality in order to achieve short-term
Aljohani, Ahmed
core
Self-admitted Technical Debt Prediction Using Bellwether
Abstract Context: Self-admitted technical debt (SATD) refers to the temporary workaround codes that engineers purposely leave behind before releasing software. It was developed by Potdar and Shihab to highlight intentional technical debts made by developers, to meet certain deadlines during the developmental process.
Robert Koomson +4 more
openaire +1 more source
Financial well-being advice delivered within the context of social prescribing in the UK and the Republic of Ireland. [PDF]
Newstead S +6 more
europepmc +1 more source
Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems
Technical Debt is a metaphor used to describe the situation in which long-term software artifact quality is traded for short-term goals in software projects.
McIntosh, Shane +9 more
core
Socioeconomic and economic factors affecting access and progression in medical schools: a systematic review and meta-analysis. [PDF]
Arianpoor A +17 more
europepmc +1 more source

