Metraipolis › archive › dc_98df7874dc33

Following Breadcrumbs in Code: What Accidentally Committed Ad-Hoc Logs Reveal about Developer Comprehension — arXiv:2610.11041

Source
arXiv (en)
Original
https://arxiv.org/abs/2610.11041
License (as archived)
CC0-1.0
Archived
2026-10-09T06:26:39.813Z
SHA-256 of the archived text
b07ef7915f1d543cf490d04970812bfe0d4242e3b5db1d43986e241cadc4cd58
Stable URL of this page
https://metraipolis.com/documento/dc_98df7874dc33

How to cite

Following Breadcrumbs in Code: What Accidentally Committed Ad-Hoc Logs Reveal about Developer Comprehension — arXiv:2610.11041 — arXiv (en), https://arxiv.org/abs/2610.11041 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_98df7874dc33 (Metraipolis archive dc_98df7874dc33, sha256 b07ef7915f1d543cf490d04970812bfe0d4242e3b5db1d43986e241cadc4cd58)
BibTeX
@misc{dc98df7874dc33,
  title = {Following Breadcrumbs in Code: What Accidentally Committed Ad-Hoc Logs Reveal about Developer Comprehension — arXiv:2610.11041},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2610.11041},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_98df7874dc33; sha256 b07ef7915f1d543cf490d04970812bfe0d4242e3b5db1d43986e241cadc4cd58},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2610.11041. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Developers frequently insert temporary print or log statements, known as **ad-hoc logs**, to better understand program behavior at runtime, particularly when facing unexpected issues or complex control flows. Despite being a nearly universal practice, systematic study has been limited because these logs are ephemeral: they usually remain only in local environments and are removed before code is committed, making them difficult to capture. In this work, we addressed this challenge by mining accidental commits where developers unintentionally left ad-hoc logs and later deleted them, and by analyzing live-streamed programming sessions to observe their use in practice. Using these methods, we constructed a large dataset across three major programming languages (Java, JavaScript, and Python), enabling the large-scale investigation of logging practices. Our analysis reveals both common and language-specific patterns in where and how developers rely on ad-hoc logs. Across languages, ad-hoc logs tend to appear in program regions that are harder to reason about at runtime. We also identify distinctive language-level patterns, such as frequent use in asynchronous and callback functions in JavaScript and in thread-related classes in Java. In addition, functions containing ad-hoc logs generally have higher cyclomatic complexity than the overall function population. Production logs show a similar association, consistent with logging serving as a means of observing runtime behavior in structurally complex functions. Together, these findings provide empirical insight into developers' runtime comprehension practices and offer a valuable dataset for researchers and tool builders seeking to better support debugging and logging.

Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.SE, nuovi lavori del giorno).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2610.11041 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-09T05:50:45.903Z dalla pagina https://arxiv.org/list/cs.SE/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).