Context Technical debt (TD) is a metaphor reflecting technical compromises that can yield
short-term benefit but may hurt the long-term health of a software system. Objective This …

Code smells are symptoms of poor design and implementation choices weighing heavily on
the quality of produced source code. During the last decades several code smell detection …

Bar charts are an effective way to convey numeric information, but today's algorithms cannot
parse them. Existing methods fail when faced with even minor variations in appearance …

Computational notebooks combine code, visualizations, and text in a single document.
Researchers, data analysts, and even journalists are rapidly adopting this new medium. We …

The metaphor of technical debt in software development was introduced two decades ago to
explain to nontechnical stakeholders the need for what we call now" refactoring." As the term …

CONTEXT: Whilst technical debt is considered to be detrimental to the long term success of
software development, it appears to be poorly understood in academic literature. The …

Technical debt is a metaphor introduced by Cunningham to indicate “not quite right code
which we postpone making it right”. One noticeable symptom of technical debt is …

In past and recent years, the issues related to managing technical debt received significant
attention by researchers from both industry and academia. There are several factors that …

Software startups are newly created companies with no operating history and oriented
towards producing cutting-edge products. However, despite the increasing importance of …

The metaphor of technical debt was introduced to express the trade off between productivity
and quality, ie, when developers take shortcuts or perform quick hacks. More recently, our …