Thanks to my peers for collaborating on troubleshooting technology. Three that I think are particularly useful are:
Ask three before me. This empowers kids to find their own solutions to problems and gives kids a sense that they are experts when they help their peers out.
In the same vein, the acronym DATA: Did I check it, Ask a Friend, Test again, Ask the teacher, helps give kids a framework on what troubleshooting looks like. I think this acronym would be helpful following a lesson on how to troubleshoot.
Last, I appreciate Madison's suggestion to use Google Forms as a resource in a district where all staff and students have access to Google tools. I think in elementary school, a lot of my troubleshooting tips are aimed towards my teacher peers. They have varying levels of comfort with technologies, and often fear that they won't be able to solve problems that come up stops them from trying technological innovations.
KOESTER, A. (2014). Get STEAM Rolling! Children & Libraries: The Journal of the Association for Library Service to Children, 12(3), 22–25. https://doi-org.proxy.queensu.ca/10.5860/cal.12n3.22
When thinking about a five year plan for your Library, the Horizon Report: K–12 Edition from New Media Consortium provides a good framework.
In the short-term, the report advocates STEAM learning and coding literacy. I think for my library, that will take the form of more collaborative teaching with my colleagues. I will use the hour of code initiative to spotlight coding and hook kids on the fun and creative aspects of coding. Robots and microbits could act as a focal point, or culmination of the coding week. As for inserting STEAM into the curriculum, our elementary system is very conducive to interdisciplinary approaches. Coordinating with teachers to find out what they want is a good start. I anticipate that this would lead to the creation of resource bins, or makerspace resources for select subject areas. These are solvable challenges.
The first year or two in a new position is a time to build relationships and create trust, especially around collaboration. I think coding and STEAM are conducive to building that base when new to the Teacher Librarian position.
In the middle term, the report identifies focusing on measuring learning and redesigning learning spaces. I wonder if the focus on measuring learning is an artifact of the USA's obsession with standardized testing. I think I will keep in line with BC's assessment guidelines. These are in a state of flux at the moment, and I think it is important to keep on top of them, and play a role in helping staff understand them in the context of ADST, because of the teacher librarian's leadership role in technology. Redesigning learning space seems like a wicked problem in my school. It is a full and crowded school with very little wiggle room, but some redesign plans have been discussed in my posthttps://rupertsreflections.blogspot.com/2021/10/library-possibilities.html.
In the long term, 5 years or more, the report points to advancing a learning culture of innovation, and deeper learning approaches. I think cultural shift is difficult, but very worthwhile. I use school-wide initiatives to help create a culture in the school, as well as building relationships with staff and students. I think the report is wise to make this their longest term goal. It takes a lot of sustained effort to change culture, but it is time well spent.
Here is a project that I do with my kids in TinkerCad. I combine it with a Math measurement unit. We can calculate the volume of the nameplate, and relate that to how long it takes the printer to print it. It is a good idea to do this pretty prescriptively so that no none gets lost. After that, they have time to mess with the concepts we learned. This lends itself to making iterations on the theme.
It is a good idea to prep some 'assistants' to help with this lesson. This could be some kids who express an interest, or kids from higher grades who have done it before and want to take on a leadership role.
Other things I've done with the kids are pencil toppers. It is great for a measurement unit, because if they can't measure the pencil right, then the topper doesn't fit. It is great for teaching the real world implication of accuracy in engineering.
Here are some more projects that I've done with kids.
I used https://www.tinkercad.com/ for all these projects. I found it to be intuitive, and pretty easy for kids to use. I found the printer itself to be finicky and hard to get along with. It is difficult to plan out print runs in order to get a class set done in a timely manner. I would set it to run after school and be done by morning, but one print per day isn't much. Our printer was quite loud, so if you want to run all day, it needs an isolated place where the noise won't interrupt learning.
In 1982, 15 Vic20 computers were brought to my elementary library, and my class learned how to program in Basic. We learned how to use the program Turtle to move a little turtle icon around the screen, drawing pictures. We heard rumours that you could input this program into a turtle robot and drive it around the room, but our district didn't buy that.
We worked in pairs because there weren't enough computers. We loved it. It was a social experience as well as a technological one. A month later, they packed up the computers and moved them to the next school.
Later, my friend got a Commodore 64. In those days, you could buy magazines filled with incomprehensible code. If you typed it in all night, and didn't make any mistakes, you would have a game where you would drive a little lawnmower around the screen. We thought it was so cool. This experience didn't teach us any computational thinking because programs were written in assembly language. It was the social aspect of it that we liked.
Fast forward to the 2020s, and kids still love to play with code. It is still the social aspects of it that they like. Kids will do sleepovers to code MineCraft worlds. Kids will bring in their latest mash-up videos to share. Kids will show off their Scratch creations. They help each other, peer into other programmers' code, or watch tutorials. It is the social aspect that drives them still. Yasmin B. Kafai writes about creating community around coded creations. It is an important part of any school coding experience if you want the kids to take what they learn and run with it.
The hour of code is coming on December 12. It is a great opportunity to introduce the joy of coding in a social setting to your students. I like to get my grade 5s to partner with their Kindie buddies and do unplugged coding. https://code.org/curriculum/unplugged . This is a great way to go because the big kids are the experts and don't get bogged down goofing on the computers. It is pure fun and introduces computational thinking in a social environment. Sometimes we move on to Code.org lessons for the non-reader. Sometimes the big buddies bring in games that they have made to share. Sometimes we program our micro:bits to play Rock Paper Scissors with the buddies,
I make copies of coding unplugged for all the teachers and the whole school gets into it. I direct teachers to other resources, mentor peers, or offer to teach a microbit class. Fun.
Question:
How can you create a culture of participation and sharing around the digital arts?
What role does the library play in giving students a platform for sharing their work, and what liabilities does that create for the teacher librarian?
Kafai, Y. B. (2016). From computational thinking to computational participation in K--12 education. Communications of the ACM, 59(8), 26-27.
Here is a Scratch lesson I do with grade 5 kids when teaching patterns on geometry.
Here is the pattern that the Scratch program created, about 3/4 of the way through the process.
To teach coding, I generally use code.org, which I find to be very useful for kids to learn at their own pace. I have used it for kids as young as kindergarten, and like their paper-based coding for Day of Code events.
I use https://microbit.org/ to code micro:bits. This shows some real life functionality with little computers that they can hold in their hands.
All three of these platforms use block coding, which is great for beginners. Kids can expand to other coding programs if they like.
Software note: I used ScreenCastify to create this video, and loaded it onto my YouTube channel to embed it into my Blog. You can embed ScreenCastify videos directly into your google.classroom stream without using a YouTube account.
When you look for Computational Thinking, and Robotics, grade 5 on the BC Curriculum search, not much comes up. Luckily there are some really good sources for linking Computational Thinking to the curriculum, and Robotics provides one of many tools to explore those links.
They start with a comprehensive video, defining Computational Thinking in kid-friendly language.
Key visuals help break down the four aspects of Computational Thinking even more.
I was curious where I could find these in the BC Curriculum, so I went back to the search page and looked for patterns, problem solving, plan, and other language from the posters. I found those concepts were everywhere, especially in Math, LA, Science, and ADST.
For elementary, there are many good online resources to help teach coding. These may lead to coding a robot as a cumulative activity, or robots could be used as a hook to begin the unit. Here are some resources I have used:
I like to link coding with cross-curricular units. In LA, writing instructions lends itself to thinking about coding. In Science and Art, design thinking pairs well with robotics and Computational Thinking. Math pattern units are a great time to introduce programming concepts.
My school district resource centre lends out robots. At the moment, we are using BeeBots with primary grades to think about how to make effective instructions. I use coding and micro:bits in grade 5, and couple it with my simple machines unit.
I think it is a trap to see robots as the be all and end all of teaching computational thinking. For my kids, the world if full of real life examples of computational processes that are easy to incorporate into the outcomes of the curriculum. Though programing robots is a tonne of fun and a good hook to get kids interested in science.
Questions:
Are robots overrated compared to the other tools we have for teaching computational thinking?
What skills do my middle school and high school colleagues think that we should focus on in elementary school?