|
|
|
|
|
by noamyoungerm
3936 days ago
|
|
I don't get why people always think that "programming for kids" has to be done with blocks and drag-drop interfaces. It feels like it limits the complexity of what you can build to what fits on a screen, and makes applying anything beyond basic programming logic (like functions) more complex. It also feels like talking down to them instead of letting them experience an actual challenge. I think it would be far more pedagogically correct to build a simple scripting language than to limit kids to these interfaces. If it weren't for the sheer age of it, I'd still recommend http://tedfelix.com/qbasic/ as a way to wrap your head around the basics. |
|
For young kids, the problem with traditional languages is that you have to spend a huge amount of time dealing with syntactical issues like whitespace, nesting brackets, the right kinds of colons, singe/double quotes, etc, etc on any non-trivial program. I've taught my girls (10 and 11) a little Python, but kept it small scale largely because of this. On the other hand they can create pretty complex interactive animations in Scratch without having to deal with any of that, because they can focus their attention on the logic and the functionality of the commands.
I suspect that once they get to 12 or 13 this will be less of an issue, and my eldest coped with the syntax issues better than her sister when writing a bit of Python, but when they first started learning Scratch at age 8 and 9 I think it would have been extremely challenging for them to use something like Python or BASIC.