MétaCan
Menu
Back to cohort
Record W4288627348 · doi:10.48550/arxiv.1901.07024

Temporal Discounting in Technical Debt: How do Software Practitioners\n Discount the Future?

2019· preprint· W4288627348 on OpenAlex
Christoph Becker, Fabian Fagerholm, Rahul Mohanani, Alexandros Chatzigeorgiou

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenuearXiv (Cornell University) · 2019
Typepreprint
Language
FieldComputer Science
TopicOpen Source Software Innovations
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsTechnical debtDiscountingTemporal discountingIntertemporal choiceBlueprintEconomicsDynamic inconsistencyEmpirical researchSoftwareMicroeconomicsComputer scienceEconometricsSoftware developmentFinanceEngineering

Abstract

fetched live from OpenAlex

Technical Debt management decisions always imply a trade-off among outcomes\nat different points in time. In such intertemporal choices, distant outcomes\nare often valued lower than close ones, a phenomenon known as temporal\ndiscounting. Technical Debt research largely develops prescriptive approaches\nfor how software engineers should make such decisions. Few have studied how\nthey actually make them. This leaves open central questions about how software\npractitioners make decisions.\n This paper investigates how software practitioners discount uncertain future\noutcomes and whether they exhibit temporal discounting. We adopt experimental\nmethods from intertemporal choice, an active area of research. We administered\nan online questionnaire to 33 developers from two companies in which we\npresented choices between developing a feature and making a longer-term\ninvestment in architecture. The results show wide-spread temporal discounting\nwith notable differences in individual behavior. The results are consistent\nwith similar studies in consumer behavior and raise a number of questions about\nthe causal factors that influence temporal discounting in software engineering.\nAs the first empirical study on intertemporal choice in SE, the paper\nestablishes an empirical basis for understanding how software developers\napproach intertemporal choice and provides a blueprint for future studies.\n

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication, Open science, Research integrity
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.837
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.005
Science and technology studies0.0010.001
Scholarly communication0.0020.004
Open science0.0070.007
Research integrity0.0010.004
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.040
GPT teacher head0.205
Teacher spread0.165 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it