Session 6: Problem Solving and Debugging
45 minutes
discussion-based
Purpose
This session is intended to build on the conversation about debugging that began over the summer. In the summer workshop, participants were introduced to the debugging process and support resources. They also practiced debugging in Web Lab. This session is an opportunity to check in on how debugging is going, share ideas, and practice debugging in Game Lab.
Objectives
- Locate and utilize the Guide to Debugging as a resource
- Practice the debugging process in Game Lab
- Identify strategies to use to support students in the debugging process
Supplies & Prep
Room Setup:
- Participants are in groups of two (same groups as the previous session)
Note: For socially distanced workshops, have participants join a virtual call with their partner so they can screen share and work together during the debugging activity.
Facilitator Supplies:
- Your local copy of CSD - Workshop 1 - Template 21-22 - Slides
Teacher Materials:
- Laptops
- Debugging Levels in code studio
- Bug Report Worksheet
- CS Discoveries Curriculum Guide 2021
Agenda
Opening Activity (15 minutes)
Practice Debugging (16 minutes)
Reflection (12 minutes)
Transition (2 minutes)
Facilitation Guide
Opening Activity (15 minutes)
(1 minute) Opening Remarks
Remarks
As you likely noticed in the model lesson, as we begin adding more complexity to our programs in Game Lab, more opportunities for bugs arise. One common barrier to supporting students during a programming unit is knowing how to support them effectively when they encounter bugs while programming. After lunch we will transition more fully to looking at the curriculum, but first we dig deeper into the process of debugging in order to equip ourselves to effectively support students during the debugging process. We will also explore the role of the teacher in guiding students through the debugging process.
(1 minute) Journal
Prompt: How is debugging going so far? What routines have you put in place to help your students when they encounter bugs?
(6 minutes) Share Out
As participants share out add notes to the shared slide deck.
(6 minutes) Reflect and Discuss
Remind participants about the resources available to them to support students in the debugging process.
- Direct participants to the debugging resources in Appendix C of the CS Discoveries Curriculum Guide 2021
In the model lesson we just completed, which of the steps from this guide did you find yourself taking when you encountered issues or bugs?
- (2 minutes) share with your partner
- (2 minutes) whole group share out
(1 minute) Transitional Remarks
Remarks
Facilitator Tip
When learners complete the bug report in their journals, they are creating a resource that will be able to reference later if they encounter a similar bug. (Role of the Teacher: Help students organize their new knowledge in a way that can be accessed as a resource later)
You will now have the opportunity to practice debugging with a partner. One partner will be the driver and one partner will be the navigator. The navigator should use the debugging guide as a resource to guide the debugging process. The driver will take direction from the navigator in making modifications to the Game Lab code. I will keep time and let you know when it is time to switch roles. For each bug, you will complete a bug report in your journal. Both the driver and the navigator should complete the bug report in his or her individual journal.
Practice Debugging (16 minutes)
Facilitator Tip
Circulate the room and support participants as needed (be careful not to fix the bug for them, instead help them work through the process of debugging)
- Keep time (roles should change halfway through the activity)
- Keep Moving (It is important for the participants to see that the teacher plays an active role during a programming unit.)
- Challenge participants that move through the activity to think through how they might create a culture of debugging in their classroom. It is important that every participant is successful at debugging at least one of the examples before you move on to the reflection. Support participants as needed.
- Participants work in pairs to complete the bug examples. One partner will be the driver and one partner will be the navigator. The navigator should use the debugging guide as a resource to guide the debugging process. The driver will take direction from the navigator in making modifications to the Game Lab code. Participants will switch roles every 4 minutes. (The last round will only be two minutes).
- Participants should complete a bug report for at least one example bug. This should be done in their journal. Each participant should write a bug report in their individual journals.
Facilitator Note The bug report worksheet is linked on the second page of the "Guide to Debugging." Have participants navigate to this document from the link within the guide to ensure participants know where this resource is located for future use.
Reflection (12 minutes)
(4 minutes) Pair Programming and Debugging
- (1 minute) Journal: How does pair programming support the process of debugging?
- (3 minutes) Table Talk: Discuss the journal prompt as a table. The facilitator should circulate and listen in. If large scale clarification is needed, the facilitator can bring the group together to discuss.
(4 minutes) Debugging Resources
- (1 minute) Journal: If a student has gone through the entire debugging process and still has not been successful in finding and fixing a bug, what additional resources and supports can you use to guide your student?
Discussion Goal
It is important that participants leave this session feeling confident in their ability to guide students through the debugging process even if they are new to CS. This prompt is an opportunity to remind participants that they are a part of a larger CS community with extensive knowledge and resources.
- (3 minutes) Whole Group Share Out: During this time, the facilitator should add notes to the shared slide deck.
(4 minutes) Role of the Teacher
- (1 minutes) Journal: What is the role(s) of the teacher in the debugging process?
- (3 minutes) Whole Group Share Out: As participants share out with the whole group, the facilitators adds to the “Role of the Teacher” poster from the opening session.