One extra CodeHealth point is associated with 3.5% to 6.1% lower agent review-and-fix token cost, but the association is absorbed when the total size of the scored files is added to the model.
hub
Journal of Systems and Software 101:193--220
10 Pith papers cite this work, alongside 724 external citations. Polarity classification is still indexing.
10
Pith papers citing it
724
external citations · external index
hub tools
citation-role summary
background 2
citation-polarity summary
roles
background 2representative citing papers
A five-workshop action research program helped an embedded software team adopt technical debt management, with backlog reminders sustaining awareness better than workshop information alone.
A 6-week observational case study conceptualizes how a multidisciplinary data-intensive team identifies, assesses, treats, and breaks down technical debt to fit sprint capacity.
Negative sentiment in self-admitted technical debt comments causes a minority of developers to rate the debt as higher priority than an otherwise similar neutral comment.
Design smells such as cyclic dependencies and missing encapsulation measurably alter software practitioners' self-reported valence, arousal, and dominance, with cyclic dependencies causing the strongest displeasure.
A practitioner study with 11 participants produces a six-family taxonomy of stakeholder criteria for technical debt decisions, distinguishing acquisition from repayment functions.
ML-specific code smells occur 41-94 times less often than general Python smells in 279 projects, with associations to commit frequency and domain but none for general smells or most other project characteristics.
A multivocal review of 108 studies finds architectural degradation is a socio-technical process whose measurement is well supported but whose continuous remediation is largely missing.
A Dagstuhl workshop manifesto that consolidates technical debt management into ten principles and a five-phase roadmap, emphasizing value, architecture, and socio-technical factors.
citing papers explorer
-
CodeHealth Predicts the Token Cost of Agentic Code Review: A Pre-Registered Study of 465 Agent-Authored Pull Requests
One extra CodeHealth point is associated with 3.5% to 6.1% lower agent review-and-fix token cost, but the association is absorbed when the total size of the scored files is added to the model.
-
Establishing Technical Debt Management -- A Five-Step Workshop Approach and an Action Research Study
A five-workshop action research program helped an embedded software team adopt technical debt management, with backlog reminders sustaining awareness better than workshop information alone.
-
Managing Technical Debt in a Multidisciplinary Data Intensive Software Team: an Observational Case Study
A 6-week observational case study conceptualizes how a multidisciplinary data-intensive team identifies, assesses, treats, and breaks down technical debt to fit sprint capacity.
-
Negativity in Self-Admitted Technical Debt: How Sentiment Influences Prioritization
Negative sentiment in self-admitted technical debt comments causes a minority of developers to rate the debt as higher priority than an otherwise similar neutral comment.
-
Measuring affective states from technical debt: A psychoempirical software engineering experiment
Design smells such as cyclic dependencies and missing encapsulation measurably alter software practitioners' self-reported valence, arousal, and dominance, with cyclic dependencies causing the strongest displeasure.
-
Stakeholder Criteria in Technical Debt Decision-Making: A Practitioner-Informed Taxonomy
A practitioner study with 11 participants produces a six-family taxonomy of stakeholder criteria for technical debt decisions, distinguishing acquisition from repayment functions.
-
Comparing ML-Specific and General Python Code Smells Across Project Characteristics
ML-specific code smells occur 41-94 times less often than general Python smells in 279 projects, with associations to commit frequency and domain but none for general smells or most other project characteristics.
-
Architectural Degradation: Definition, Motivations, Measurement and Remediation Approaches
A multivocal review of 108 studies finds architectural degradation is a socio-technical process whose measurement is well supported but whose continuous remediation is largely missing.
-
Manifesto from Dagstuhl Perspectives Workshop 24452 -- Reframing Technical Debt
A Dagstuhl workshop manifesto that consolidates technical debt management into ten principles and a five-phase roadmap, emphasizing value, architecture, and socio-technical factors.
- SWE-Prometheus: Measuring Engineering Governance Improvements in Real-World Repositories