Luis Morales-Navarro, Deborah Fields, Yasmin B. Kafai and Deepali Barapatre
The purpose of this paper is to examine how a clinical interview protocol with failure artifact scenarios can capture changes in high school students’ explanations of…
Abstract
Purpose
The purpose of this paper is to examine how a clinical interview protocol with failure artifact scenarios can capture changes in high school students’ explanations of troubleshooting processes in physical computing activities. The authors focus on physical computing, as finding and fixing hardware and software bugs is a highly contextual practice that involves multiple interconnected domains and skills.
Design/methodology/approach
This paper developed and piloted a “failure artifact scenarios” clinical interview protocol. Youth were presented with buggy physical computing projects over video calls and asked for suggestions on how to fix them without having access to the actual project or its code. Authors applied this clinical interview protocol before and after an eight-week-long physical computing (more specifically, electronic textiles) unit. They analyzed matching pre- and post-interviews from 18 students at four different schools.
Findings
The findings demonstrate how the protocol can capture change in students’ thinking about troubleshooting by eliciting students’ explanations of specificity of domain knowledge of problems, multimodality of physical computing, iterative testing of failure artifact scenarios and concreteness of troubleshooting and problem-solving processes.
Originality/value
Beyond tests and surveys used to assess debugging, which traditionally focus on correctness or student beliefs, the “failure artifact scenarios” clinical interview protocol reveals student troubleshooting-related thinking processes when encountering buggy projects. As an assessment tool, it may be useful to evaluate the change and development of students’ abilities over time.
Details
Keywords
Colin Hennessy Elliott, Alexandra Gendreau Chakarov, Jeffrey B. Bush, Jessie Nixon and Mimi Recker
The purpose of this paper is to examine how a middle school science teacher, new to programming, supports students in learning to debug physical computing systems consisting of…
Abstract
Purpose
The purpose of this paper is to examine how a middle school science teacher, new to programming, supports students in learning to debug physical computing systems consisting of programmable sensors and data displays.
Design/methodology/approach
This case study draws on data collected during an inquiry-oriented instructional unit in which students learn to collect, display and interpret data from their surrounding environment by wiring and programming a physical computing system. Using interaction analysis, the authors analyzed video recordings of one teacher’s (Gabrielle) pedagogical moves as she supported students in debugging their systems as they drew upon a variety of embodied, material and social resources.
Findings
This study presents Gabrielle’s debugging interactional grammar, highlighting the pedagogical possibilities for supporting students in systematic ways, providing affective support (e.g. showing them care and encouragement) and positioning herself as a learner with the students. Gabrielle’s practice, and therefore her pedagogy, has the potential to support students in becoming better debuggers on their own in the future.
Originality/value
While much of the prior work on learning to debug focuses on learner actions and possible errors, this case focuses on an educator’s debugging pedagogy centered on the educator debugging with the learners. This case study illustrates the need for educators to exhibit deft facilitation, vulnerability and orchestration skills to support student development of their own process for and agency in debugging.