Hour of Code Reflections

The preparation for this year's Hour of Code was a lesson in perseverance. I was determined to find just the right activity for each grade level. Because coding has become more popularized, the number of activities that are available at no cost for students is incredible. However, with choice comes research. I must have tested out a minimum of 40 different activities for my students. I would think I found the perfect match and then get to lesson/level 3 and realize that they were jumping from basic sequencing in an algorithm to loops, and then quickly moving on to writing conditionals in lesson 5. All of this would be fine if the activity were meant for a 4-5th grader that has had exposure to coding and just needed a jumpstart review, but the look and feel would be for a first or second grader.

After a month of planning, I had a "menu" of activities laid out for grade levels to start the week. To say I wasn't nervous would be dishonest! Gauging the individual needs of each student in each grade level from K to 8 and planning a preview lesson that was short and sweet, engaging, appropriate, and sufficient for the task at hand was a challenging task. I think I had 6 different drafts of lesson plans for my students, but I still didn't feel completely sure it would be right!

In the end, I can say that the week went well overall. As I had grade levels for the second time, things went more smoothly as I tinkered with my lessons and language. Some classes were less productive than others, but for the most part I was impressed by the level of learning and collaboration that was happening.

On many occasions, I found myself grinning ear to ear watching a student "get it" for the first time. My heart soared watching a struggling student take on the role of teacher with pride. I challenged my own misconceptions about student levels and interests as I watched them problem solve, persevere, and succeed.

My Reflections:

1. Kids should have exposure to coding more than once a school year.

2. The ones that shine are often the ones that you least expect. This needs to be capitalized upon.

3. Tech Class needs to become more individualized and involve more choice and self-directed projects once students hit middle school. Why do we need to wait until high school and beyond to let students go where their interests take them?

4. Just like everything in life, some students either do not enjoy coding or need to code in private!

5. Coding seems to naturally bring out the best in students in terms of collaboration, patience for each other, and kindness.

6. Coding requires perseverance. This needs to be central to the conversation from day 1. You will fail and it will happen often. Knowing when to ask questions is key.

7. I cannot possibly learn enough, quickly enough for my liking!