characterize debugging strategies

Designs and applies analyses, observational protocols, and measurement instruments to characterize how people detect, diagnose, and recover from faults in programs or interactive systems. Work includes building taxonomies of recovery strategies, coding debugging behaviors (e.g., intent clarification, code tracing), quantifying strategy preferences, and relating error types to chosen recovery actions.

characterizedebuggingstrategies

Recent Skill Trend

Momentum and market value over time
Trending
Score
No comparison yet
0.57
Oct 01, 2026Oct 01, 2026
Career
Value
No comparison yet
$200K/year
Oct 01, 2026Oct 01, 2026

Recommended Survey Paper

Quick overview of the field
View more

Must-Read Papers

Most classic and influential ideas
View more

Existing debugging tools excel at verifying hypotheses but struggle to support hypothesis generation, as programmers must manually reconstruct the program’s state evolution. This work proposes a novel debugging paradigm centered on complete execution traces, leveraging program tracing techniques to record and temporally visualize the actual code paths executed, rather than relying on the static structure of the source code. By presenting runtime behavior in a chronological and contextualized manner, this approach significantly enhances the comprehensibility of program execution, thereby facilitating more efficient hypothesis generation during debugging. We implement a prototype system and conduct preliminary experiments that demonstrate its effectiveness in improving program understanding efficiency, while also uncovering key challenges and promising directions for future research.

debuggingexecution tracehypothesis generation

This work addresses the limited interpretability of large language model–driven automated program repair, which hinders diagnosis and reproducibility of failure cases. To this end, we present TraceView, the first interactive visualization tool that structures repair trajectories into Thought-Action-Result triplets and supports semantic relationship annotation. By integrating trajectory parsing, relational modeling, and graph-based visualization techniques, TraceView enables traceable analysis from high-level overviews to fine-grained details. A user study demonstrates that TraceView significantly enhances developers’ comprehension of the repair process and improves navigation efficiency. The implementation and a demonstration video are publicly available.

automated program repairfailure diagnosisinteractive visualization

This work addresses the inefficiency of general-purpose language agents in self-repair, which often stems from a lack of fine-grained failure diagnosis, leading to blind context expansion and conflation of distinct error types. To overcome this, the authors propose DARC, a novel framework that prioritizes diagnosis before repair: it first analyzes failure patterns across a task family using a development set, selects appropriate repair interventions, and employs a validator to freeze the optimal success-cost strategy, thereby enforcing a causal “diagnose-then-repair” workflow. By designing recovery-oriented interfaces that integrate failure mode analysis, pruning of a shared repair library, and strategy freezing, DARC significantly improves task success rates while reducing interaction steps or retrieval overhead across diverse environments—including ALFWorld, AppWorld, and XBRL Finance—outperforming both standard foundation agents and existing general-purpose repair methods.

agent failuresdiagnostic signalsfailure modes

This study addresses the high cognitive load and attentional depletion developers experience during debugging, which threaten project sustainability. Grounded in cognitive science, it conceptualizes debugging as a cognitive process of constructing mental models that explain anomalous system behavior. Through semi-structured interviews with 27 professional developers and employing a constructivist grounded theory approach, the research systematically uncovers, for the first time, the neural and attentional mechanisms underlying the experience of confusion during debugging. The resulting empirically grounded cognitive theory of debugging elucidates the intrinsic relationships among debugging difficulty, cognitive resource consumption, and development sustainability. This work provides a theoretical foundation for developer experience research and offers practical guidance for industry efforts to optimize debugging tools and workflows.

cognitive fatiguedebuggingdeveloper experience

Hot Scholars

ZC

Zhenpeng Chen

Research Fellow, Nanyang Technological University
Software EngineeringMachine LearningData ScienceTrustworthy AI
YW

Yong Wang

Assistant Professor, Nanyang Technological University
Data VisualizationHCIHuman-AI CollaborationFinTech
YX

Yixuan Xie

School of Eletrical Engineering and Telecommunication, University of New South Wales, Sydney
Communication/Coding theory/Iterative process
JS

Jimeng Shi

Postdoctoral researcher, University of Illinois Urbana-Champaign
AI for Science & EngineeringLLMsDiffusion ModelsText Mining