CLCYSENov 1, 2025

Reasoning Trajectories for Socratic Debugging of Student Code: From Misconceptions to Contradictions and Updated Beliefs

arXiv:2511.00371v1h-index: 9
Originality Incremental advance
AI Analysis

This addresses the challenge of automating Socratic debugging for novice programmers, though it is incremental as it builds on existing LLM capabilities for educational tasks.

The paper tackles the problem of generating guided reasoning trajectories for Socratic debugging of student code, where instructors help students identify bugs caused by misconceptions. The result shows that frontier models can generate up to 91% correct reasoning trajectories and 98.7% valid conversation turns.

In Socratic debugging, instructors guide students towards identifying and fixing a bug on their own, instead of providing the bug fix directly. Most novice programmer bugs are caused by programming misconceptions, namely false beliefs about a programming concept. In this context, Socratic debugging can be formulated as a guided Reasoning Trajectory (RT) leading to a statement about the program behavior that contradicts the bug-causing misconception. Upon reaching this statement, the ensuing cognitive dissonance leads the student to first identify and then update their false belief. In this paper, we introduce the task of reasoning trajectory generation, together with a dataset of debugging problems manually annotated with RTs. We then describe LLM-based solutions for generating RTs and Socratic conversations that are anchored on them. A large-scale LLM-as-judge evaluation shows that frontier models can generate up to 91% correct reasoning trajectories and 98.7% valid conversation turns.

Foundations

The foundational work for this paper's niche, ranked by how specifically the neighbourhood builds on it — not by global fame.

Your Notes