Visual block-based programming environments allow elementary school students to create their own programs in ways that are more accessible than in textual programming environments. These environments help students write code by removing syntax errors and reducing typing. Students create code by dragging, dropping, and snapping constructs together (e.g. blocks) that are organized by lists, colors, shape, images, etc. However, programming in visual block-based environments is not always simple; in fact, it can become complex quickly. In addition to elements that create code, the visual aspects of these environments provide readers information about what happens, when, and how. Here, we focus on how students used visual cues when reading programs in our block-based programming environment, LaPlaya, a variant of Scratch. Specifically we identified the visual cues students noticed and acted upon. These included not only those that were intended by designers (perceptible affordances), but also those that were not intended by designers (false affordances). Through a detailed content analysis of 13 focus groups with fourth graders we created an initial taxonomy of visual cues in our programming environment and explored how students used these cues to make predictions about provided code, and the types of affordances such cues offered students.
This article integrates an ecological approach and design-based research in computer science education research by following the simultaneous development of a computer programming environment and curriculum for elementary school age children over 2-1/2 years. We studied the alignment of the affordances provided by the programming environment and curriculum with the effectivities of students in 4th through 6th grade (9-12 years old). We used the computer science concept of initializing as a tracer idea and both qualitative and quantitative data to identify mismatches between the affordances provided by our programming environment and the learners’ effectivities. These included requisite mathematical skills, confusion between resetting and setting up, and incorrectly assuming that features of the programming environment conveyed information. We then describe how we addressed the mismatches by removing or adding functionality to the programming environment, adding signifiers, adapting the curriculum to include scaffolding related to the effectivities, or removing activities.