Cindy’s Tech Test Kitchen

Cindy and I have a professional relationship that allows us to develop K-12 classroom ideas for technology integration. We approach our goals through a collaboration that allows each of us to take different approaches. This works well as long as the approaches are complimentary. Back in the day when “cooperative learning” was an “in thing”, this was called a jigsaw model. I have provided a link in case this trend had its day before your time. Cindy learns by doing and I learn by thinking (sometimes out loud). This means I do most of the writing.

Here is a recent exploration into the potential of “mini programmable robots”. We picked up an Ozobot at a recent conference and have spent just enough time with it since to understand some of the basics. An Ozobot is small – about the size of golf ball. It can be programmed in several different ways. One approach feeds instructions to the mobile bot through color codes imposed on the line that it is following. Different color patches on the line tell it to speed up, slow down, etc. Now the demos for this are suited to the size of the Ozobot – i.e., small. It might be asked to follow a pattern on the surface of an iPad.

What if instead of duplicating the typical small scale projects the company offers as examples you decide to apply a few basic principles to a project of your own design. What if instead of the surface of an iPad or a sheet of paper, you decide to build a lego city in your basement and allow the Ozobot to explore the city.

Cindy had a collaborator in this project. Some of our grandchildren were visiting and Preston likes “science” and legos. It turns out the kids think on a different scale than rational adults. None of this start small and then build up kind of thing.

ozostructures

I must say I would have started with the robot and figured it out first, but Preston wanted to build the city first.

ozoplan

There was a plan (if you can read it). The plan specifies the structures to be included in the lego city.

ozotrack

Now, it was time to construct the road (track). The idea was to cut sheets of paper in half and then tape them together.

ozotest

Here is the closest thing to a test of concept. You can see the sheet to the left that explains the different color codes. We did learn that the width of the line is important. If the line is too narrow, the bot just stops.

ozoonroad

Here you see the robot on part of the road. One unanticipated problem concerned the method for joining the paper strips. When taping the pieces together, one sheet must overlap the other. It turns out it takes very little to stop the small robot. If it runs into the end of the next strip it stalls. This is not an issue as long as the direction of travel moves from the overlapping piece of track to the underlapping (is this a word) piece of track. Now if the track moves in a circle you soon figure this out and all would be well. However, if you decide to have the robot come to a turn in the road (and take the path less traveled) the problem of having all of the road moving in a predictable direction became an issue. The finished product contained several “bugs”, but like some software I have used it worked most of the time.

ozolast

My mom had this expression she applied to me when I was allowed to dish up my own food when kids were allowed to make such decisions at a pot luck or some other event. She would say – “see, your eyes are bigger than your stomach”. I wish this was still the case. Anyway, this project was far larger than it should have been for a learner of Preston’s age. We spent hours and hours over two days taping slips of paper together and then retaping sections when we understood that adjoining pieces of paper had to be connected in a certain way or when little sister walked through the lego village dragging her feet and messing up the road. Once constructed, there was probably far less interest in exploring and debugging than probably would have been the case should the adults involved have excercised more control over the scope of the project.

One of the issues I think is important when it comes to project based learning is the efficiency of the project. When should an educator “scaffold” a project to increase efficiency? How much independence should learners be given and what are the benefits and costs of frustration and failure? These seem to be current educational issues and I could see these issues play out as I spent several hours cutting 3 inch sections of tape for the workers to use in the construction process.

Loading

The meaning of “circle”

This is my contribution to the week of code.

One of the things I remember from reading Papert (Mindstorms I think) was his explanation of different ways of understanding. He claimed that computation offered a different way of understanding. One example which I think was from the same source concerned the understanding of circle. The demo goes something like this.

Most of probably remember the definition of circle – a closed plane figure consisting of all points equidistant from a point. The ability to produce this definition does not really mean we understand it. He proposed the following demonstration (I hope I am remembering the source appropriately). You can turn this definition into a program (logo).

blockly

 

This demo was generated in Blockly. If you follow the code, you should be see how the code expresses the definition.

Loading

LOGO reaches middle age

You may be of the impression that technology in education is a recent phenomenon. You may also be surprised to learn that we have reached the 40th birthday of LOGO. If you don’t know what LOGO is, you must also be a digital native – one of those folks who assumes he/she is a natural user without really experiencing the changes that have brought us to the point where we are today. The origin of LOGO was a little before my time as an active computer user, but I did have experience with LOGO as an educational application.

So, for you Web 2.0 digital newbies, I dug a few LOGO images out of the vault. LOGO was a very capable language that was typically used at a very simple level to allow students to experience a “computational” perspective on geometry and learn some fundamental programming skills.

LOGO Turtle

A program/script might look something like this (after defining square):

TO BLACKHOLE :SIDE

SQUARE :SIDE

RT 12

Make “SIDE :SIDE*.985

IF :SIDE.5 [STOP]

BLACKHOLE :SIDE

END

LOGO Turtle

Time for this old man’s afternoon power nap. 😉

Loading

NECC 2007 – Sharing

What is it that prompts individuals to share resources they have had to invest a great deal of time and expertise to create?

Today, I attended a session on the future of the book. While the general opinion appeared to be that the traditional book can no longer serve as the only source of information, there appears to be little consensus on what else should be available and how the development of these other resources should be financed. A teacher who relies on self-generated content was on the panel and presented samples of her materials. She contends that teachers are typically willing to share as long as other teachers reciprocate. I wonder. How many teachers would be willing to participate and how could it be assured that the requires types of content would be created. Can the open source model somehow be adapted to provide the content necessary for K-12 instruction?

The comment on sharing made me think of a session we attended yesterday. Mitchel Resnick from MIT was describing the work being done with Scratch. If you have not been exposed to Scratch, it is a visual environment within which the behavior of objects can be scripted (programmed). Programs are not developed using a language consisting of words, but rather objects. The objects are organized and interrelated by the programmer. The idea is to create a simple way to program that can produce impressive and thus motivating projects. Scratch is a free product. In addition to the software, the creators offer a site participants can use to upload completed projects.

The Scratch team has noticed something interesting about how the site has been used. Students download a project from the site, see how the project was coded, add an improvement of their own, and then upload the improved project back to the site. It is kind of a training ground for open source software developers. Put your project on the site and expect other people to modify your work. Maybe this is not only a way to reintroduce programming into the curriculum, but also a way to develop an appreciation of sharing.

Blogged with Flock

Loading