SoylentNews

quietus [soylentnews.org] writes:

The other thing is that in order to learn, children need to have fun. But they have fun by really being pushed to explore and create and make new things that are personally meaningful. So you need open-ended environments that allow children to explore and express themselves.

(This Inventor Is Molding Tomorrow’s Inventors, IEEE Spectrum [ieee.org])

IEEE Spectrum has a (short) sit-down with Marina Umaschi Bers, co-creator of the ScratchJr [scratchjr.org] programming language and the KIBO robotics kits [kinderlabrobotics.com]. Both tools are aimed at learning kids to code and develop STEAM skills [schoolspecialty.com] from a very young age. Other examples of such tools are the mTiny robot toy [makeblock.com] and the Micro:bit computer [microbit.org].

Being able to code is a new literacy, remarks Professor Bers, and like with reading and writing, we need to adapt our learning tools to children's developmental ages. One idea here is that of a "coding playground" where it's not about following step-by-step plans, but about inventing games, pretend play and creating anything children can imagine. She is currently working on a project [bc.edu] to bring such a playground outside: integrating motors, sensors and other devices in physical playgrounds, "to bolster computational thinking through play".

Given how fast complicated toys are being thrown aside by young children, in contrast to a simple ball -- or a meccano set, for the engineering types -- I have my doubts.

At least one of the tools mentioned above is aimed at todlers. So put aside your model steam locomotive, oh fellow 'lentil, and advice me: from what age do you think we should try to steer kids into "coding" or "developing", and which tools should or could be used for this?

Feel free to wax nostalgic about toys of days past, ofcourse, in this, one of your favorite playgrounds: the soylentnews comment editor.

Original Submission