MétaCan
Menu
Back to cohort
Record W4392564511 · doi:10.1145/3626252.3630934

Stump-the-Teacher: Using Student-generated Examples during Explicit Debugging Instruction

2024· article· en· W4392564511 on OpenAlex

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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicTeaching and Learning Programming
Canadian institutionsSimon Fraser University
Fundersnot available
KeywordsDebuggingAlgorithmic program debuggingComputer scienceProgrammerProgramming languageMathematics educationThink aloud protocolUsabilityPsychologyHuman–computer interaction

Abstract

fetched live from OpenAlex

As the number of upper-elementary students (grades 4-7) interested in computer programming increases, there is growing interest in age-appropriate pedagogical approaches to debugging instruction. However, previous research findings with younger novice learners are limited, and research with explicit debugging instruction has shown limited uptake by students. This experience report describes two novel classroom activities undertaken as part of an investigation into explicit debugging instruction with upper-elementary-aged students: student-generated examples (SGE), in which students modified working programs by purposefully introducing bugs; and stump-the-teacher, in which the teacher demonstrates their expert debugging approach explicitly by thinking aloud while attempting to debug the SGEs. Students demonstrated both an eagerness to craft examples that they hoped would stump the teacher and actively engaged with the live-debugging exercise. Students were also asked to compare and describe their own debugging approach to the teacher's debugging approach. Analysis of the bugs deliberately introduced by students found that they were primarily syntax-related, in line with early novice programmer error patterns. Additionally, student comparisons of their debugging approaches demonstrated awareness and engagement by most students, as well as possible early indications for disengaged or overwhelmed students. Further, analysis of later student debugging behavior on exercises showed students following the "run first, run often" approach demonstrated by the teacher. These findings suggest that engaging students in explicit debugging instruction can provide insights into their engagement and confidence levels, as well as encourage them to self-reflect and improve their debugging approaches.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.914
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.000
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.038
GPT teacher head0.298
Teacher spread0.260 · 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

Quick stats

Citations3
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicTeaching and Learning ProgrammingFrench-language works237,207