|
|
|
|
|
by alok-g
4795 days ago
|
|
Does anyone have any recommendations on at what minimum age should this be introduced to kids? The website recommends 8-16 years, but then I was doing real programming at the age of ten, so eight may not be the best answer. My son is five right now. Introducing too early seems to have a downside that if my son does not like it (or cannot grasp it), he develops a negative feeling towards it like boredom or else, and then subconsciously does not want to return to it even at the right age. |
|
(Note that we mix kids, with ages ranging from 5 to 14, and always a 50/50 ratio of girls/boys, not via quota but because of the way the events are planned. So we also have older kids. It's good for the younger ones.)
At this age, they (usually) don't read, so they generally are working with an adult and another kid, or in some instance with an older kid (my just 6 years old daughter for example worked one of the firs times with an older girl that knew Scratch.)
A very important thing to do is to let the creative direction to the kids. Don't force the programming of a shooter on them. They have lot of ideas, and they will be more motivated if the idea come from them. Also they will be proud to see it happen. They'll want to move things, animate, etc. They'll want to copy things they have seen. Letting them draw on paper, for example a character, then taking a picture and incorporating it in Scratch is a nice way to alternate between two different activities (solving the "will they focus for long?" question)
If you want to know more: http://codinggouter.org and my talk at FOSDEM: https://fosdem.org/2013/schedule/event/coding_gouter/ may be helpful