I'm working on getting a little more organized for substitutes and such. I have started a document that gives general guidelines for different materials in the lab and classroom management techniques. My classroom setup is that of a specialist. I see 22 classes each week, 1st - 5th grades for one hour and kindergarten for a half an hour. There are four classes each of kindergarten through 3rd grade with a maximum of 24 students in each class. There are three classes each of 4th and 5th grades with a maximum of 32 students in each class. At each grade level there are approximately 96 students. This poses challenges for project storage and managing materials that are shared at a grade level and between grade levels. Below is the link to the live document as I create it. Feel free to take a look and also check back for updates and improvements.
Showing posts with label WeDo. Show all posts
Showing posts with label WeDo. Show all posts
Saturday, May 12, 2018
Saturday, September 2, 2017
Global Conference on Educational Robotics
It was a busy summer with professional opportunities. So busy, that it has taken almost three months to have time to share. The first two weeks of the new school year are behind me. As usual, I will be making changes based on the new information on instructional practices I have learned throughout the summer. One big change is moving my robotics instructions for fourth and fifth grade students, as well as my after school groups, towards the Junior Botball robot (https://www.juniorbotballchallenge.org/).
I have tried and used various robotics platforms during elementary engineering instruction, after school groups, and makerspace. LEGO robotics, WeDo and Mindstorms, have been the predominant robotics used. These are fantastic because they come with a variety of curriculum and are easy to start using whether experienced with robotics or not. Other robotics formats include Cubit and Edison. All of these platforms have pros and cons. The Cubit robot is a platform that allows students to see the inner components of the robot and demystifies the hardware components. Edison robots are easy to use and do not require any formal programming since the robot can scan programmed bar-codes to program the robot for specific tasks. In fact, these robots were used to hold a school-wide sumobot challenge because students of all ages could program the robots either using the bar-codes or drag and drop. In fact, all of the robots, LEGO, Cubit, and Edison, use a drag and drop programming platform. Junior Botball is the first robotics platform I have experienced that is designed for students from kindergarten through high school and requires the students to program in C++ or Python.
Junior Botball does not use a drag and drop interface but instead teaches the students a programming language. I was able to see students as young as first grade programming at the Global Conference on Educational Robotics (GCER). The competition portion of GCER (http://new.gcer.net/) had different divisions including elementary, middle school/high school, and adult. In addition to the competition, GCER held various sessions for coaches and students. The sessions included how to implement Junior Botball, programming and engineering instruction, and much more. The overall feel of GCER was that of a learning experience. This was one of the best aspects of competing in the Junior Botball division at GCER. The students worked to complete individual challenges rather than competing against another team. This approach helped to build friendships between the different teams and allow students to work towards their personal bests. So, not only were elementary students' fingers flying over the keyboards programming in C++ or Python, but participants were also placed in a low stress situation of learning that could be as competitive as students wanted. This was a refreshing experience compared to other student competitions I have participated in as a coach. I look forward to growing my Junior Botball group and school and seeing students walk away from the program with an actual programming language in their tool kit rather than just a drag and drop experience.
I have tried and used various robotics platforms during elementary engineering instruction, after school groups, and makerspace. LEGO robotics, WeDo and Mindstorms, have been the predominant robotics used. These are fantastic because they come with a variety of curriculum and are easy to start using whether experienced with robotics or not. Other robotics formats include Cubit and Edison. All of these platforms have pros and cons. The Cubit robot is a platform that allows students to see the inner components of the robot and demystifies the hardware components. Edison robots are easy to use and do not require any formal programming since the robot can scan programmed bar-codes to program the robot for specific tasks. In fact, these robots were used to hold a school-wide sumobot challenge because students of all ages could program the robots either using the bar-codes or drag and drop. In fact, all of the robots, LEGO, Cubit, and Edison, use a drag and drop programming platform. Junior Botball is the first robotics platform I have experienced that is designed for students from kindergarten through high school and requires the students to program in C++ or Python.
Junior Botball does not use a drag and drop interface but instead teaches the students a programming language. I was able to see students as young as first grade programming at the Global Conference on Educational Robotics (GCER). The competition portion of GCER (http://new.gcer.net/) had different divisions including elementary, middle school/high school, and adult. In addition to the competition, GCER held various sessions for coaches and students. The sessions included how to implement Junior Botball, programming and engineering instruction, and much more. The overall feel of GCER was that of a learning experience. This was one of the best aspects of competing in the Junior Botball division at GCER. The students worked to complete individual challenges rather than competing against another team. This approach helped to build friendships between the different teams and allow students to work towards their personal bests. So, not only were elementary students' fingers flying over the keyboards programming in C++ or Python, but participants were also placed in a low stress situation of learning that could be as competitive as students wanted. This was a refreshing experience compared to other student competitions I have participated in as a coach. I look forward to growing my Junior Botball group and school and seeing students walk away from the program with an actual programming language in their tool kit rather than just a drag and drop experience.
Subscribe to:
Posts (Atom)