1
00:00:00,380 --> 00:00:04,480
Unplugged Activity | Relay Programming

2
00:00:07,540 --> 00:00:12,100
Hi, I'm Anna! Today we're going to do relay programming.

3
00:00:12,110 --> 00:00:16,470
It's all about programming under pressure
and debugging the mistakes that sometimes

4
00:00:16,470 --> 00:00:22,430
happen when you work really quickly or in
teams. We'll use graph paper programming to

5
00:00:22,430 --> 00:00:29,430
simulate coding, and use relay races to simulate
having a deadline. In relay programming, teams

6
00:00:32,250 --> 00:00:37,660
will be racing to finish a graph paper program.
You have to check your teammate's work, or

7
00:00:37,660 --> 00:00:44,660
debug it, fix it if there's a mistake, add
your arrow, and run back and tag your teammate.

8
00:00:45,079 --> 00:00:52,079
Programmers use debugging a lot to find and
fix problems in their algorithms or code.

9
00:00:56,710 --> 00:01:01,829
There are lots of ways to debug problems.
One of the easiest is to move step by step

10
00:01:01,829 --> 00:01:08,149
until you find where something goes wrong,
then fix it. Here, I'm trying to do a back

11
00:01:08,149 --> 00:01:15,149
handspring, but I keep falling off. I walk
through each part, step by step, and realize

12
00:01:15,479 --> 00:01:22,479
where my mistake was. My coach showed me I
wasn't putting my hands on the beam correctly.

13
00:01:23,840 --> 00:01:29,020
So I tried another back handspring on the
beam with my new hand position, and I stuck

14
00:01:29,020 --> 00:01:36,020
it! I was really glad I debugged my back handspring.
We figured it out!

15
00:01:36,020 --> 00:01:40,120
Debugging is finding and fixing problems.

16
00:01:42,900 --> 00:01:44,900
Nice, Anna! Good job!