Results 11 to 20 of about 7,723 (252)
Organizing the technical debt landscape [PDF]
To date, several methods and tools for detecting source code and design anomalies have been developed. While each method focuses on identifying certain classes of source code anomalies that potentially relate to technical debt (TD), the overlaps and gaps among these classes and TD have not been rigorously demonstrated. We propose to construct a seminal
Clemente Izurieta +5 more
core +5 more sources
Investigating technical debt folklore: Shedding some light on technical debt opinion [PDF]
We identified and organized a number of statements about technical debt (TD Folklore list) expressed by practitioners in online websites, blogs and published papers. We chose 14 statements and we evaluated them through two surveys (37 practitioners answered the questionnaires), ranking them by agreement and consensus.
Rodrigo O. Spínola +4 more
core +5 more sources
Using technical debt data in decision making: Potential decision approaches
S.45-48The management of technical debt ultimately requires decision making - about incurring, paying off, or deferring technical debt instances. This position paper discusses several existing approaches to complex decision making, and suggests that ...
Vetrò, A. +6 more
core +2 more sources
Do we need to pay technical debt in blockchain software systems?
For blockchain software systems, framework developers may introduce technical debts that application developers are not aware of. Because these technical debts can have a negative impact on software projects, we need to investigate the issue of technical
Yubin Qu +6 more
doaj +1 more source
Experiences on Managing Technical Debt with Code Smells and AntiPatterns [PDF]
Technical debt has become a common metaphor for the accumulation of software design and implementation choices that seek fast initial gains but that are under par and counterproductive in the long run.
Tuovinen, Antti-Pekka +5 more
core +1 more source
This study argues the difference between security and privacy and outlines the concept of Privacy Debt as a new Technical Debt. Privacy is gaining momentum in any software system due to mandatory compliance with respect to laws and regulations. There are
Xabier Larrucea +2 more
doaj +1 more source
Technical Debt (TD) is a software engineering metaphor that resembles the production of poor-quality code to going into debt. In particular, a development team that “saves” effort while developing by not removing inefficiencies, has to ...
Nikolaos Nikolaidis +4 more
doaj +1 more source
These days, everyone uses the term technical debt. It's so prevalent that we shorten it to tech debt tech debt or even just TD. Tech debt is also hacky code, code written by novices, code written without consideration of software architecture (so-called big balls of mud), and code with antipatterns flagged by static analysis tools.
openaire +1 more source
How Reproducibility Will Accelerate Discovery Through Collaboration in Physio-Logging
What new questions could ecophysiologists answer if physio-logging research was fully reproducible? We argue that technical debt (computational hurdles resulting from prioritizing short-term goals over long-term sustainability) stemming from insufficient
Max F. Czapanskiy, Roxanne S. Beltran
doaj +1 more source
Towards an ontology of terms on technical debt
7 S.Technical debt is a term that has been used to describe the increased cost of changing or maintaining a system due to shortcuts taken during its development.
Mendes, T.S. +4 more
core +1 more source

