Day 1
01 Intros 02 CSD Overview 03 Break 04 Model Lesson 1 05 Lunch 06 Model Lesson 2 07 Lesson Assignments 08 Break 09 Lesson Planning 10 Unit 1 Wrap Up 11 Fac. Debrief
Day 2
12 Intro to Unit 2 13 Model Lesson 3 14 Break 15 Lesson Planning 16 Lunch 17 TLO 1 18 Break 19 TLO 2 20 Scavenger Hunt 21 Instructional Strategies 22 Fac. Debrief
Day 3
23 Community 24 Getting Buy-In 25 Break 26 TLO 3 27 Debugging 28 Lunch 29 TLO 4 30 Break 31 TLO 5 32 Scavenger Hunt 33 Unit 2 Wrap Up 34 Fac. Debrief
Day 4
35 Equity 36 Recruiting 37 Break 38 Unit 3 Intro 39 TLO 6 40 Lunch 41 TLO 7 42 Break 43 TLO 8 44 Scenarios 45 Unit 3 Wrap Up 46 Fac. Debrief
Day 5
47 Preparing for the Year 48 Assessment 49 Break 50 Planning 51 Lunch 52 Local Flex Time 53 Closing Ceremonies 54 End Early & Friday Facilitator Debrief

Session 27: Debugging

25 minutes

discussion-based

Purpose

Debugging is a critical skill for a programmer. This session gives critical time to develop teachers debugging skills as well as discuss how they will support students with debugging.

Objectives

  • Experience a hands on debugging activity
  • Discuss debugging techniques and know what resources exist in the course to support students and teachers in debugging

Supplies & Prep

Room Setup:

  • Normal Breakout Room Set Up
  • Teachers in pairs

Facilitator Supplies and Prep:

Teacher Materials:

Agenda

Example Debugging Task (7 minutes)

Debugging Strategies (18 minutes)

Facilitation Guide

Example Debugging Task (7 minutes)

(7 minutes) Debugging Level

Remarks

The problems you had when your HTML code did not work correctly are bugs. The process of fixing bugs and strategies used to fix them is called debugging. Today we're going to be try doing some debugging of other people's code. Debugging is the focus of the next lesson after the one we just saw.

Pair teachers up with a partner.

Have teachers visit Code Studio, Unit 2, Lesson 8 Level 2 and work with their partner to try to complete the task. If teachers complete the level quickly, they can move on to the next level, but plan to stop once everyone has completed U2 L08 Level 2.

Debugging Strategies (18 minutes)

(7 minutes) Approach to Debugging

(2 min) Think for a moment about how you have approached debugging this week, and in the activity we just did.

Reflection Prompt: What types of bugs did you find and strategies did you employ?

(5 min) Now, go and look at the Debugging Investigation Guide (found in Appendix C of the curriculum guide), which outlines four steps to debugging:

  1. describe the bug;
  2. hunt for the cause;
  3. try fixing it;
  4. document your bug

Discussion Prompt: How does this process fit with the approach you took? Discuss with the partner you worked with in the debugging activity above.

(11 minutes) Discuss: Supporting Student Debugging

Prompt: How can we help students become successful at debugging? How can you apply the four steps of the debugging investigation guide to help students learn to tackle these sorts of problems?

Remarks

Debugging and supporting student debugging is something we will continue to practice during the week and through out the year. As we continue through out the week I encourage you to keep adding debugging strategies to your list as we find new ways of the tackling the challenges we face in our code.