How computer programming languages for kids have evolved and where they're going
1–10 of 125 posts
Re: How computer programming languages for kids have evolved and where they're going
#2Does anyone know of any published research on the efficacy of this "block based programming" standard the author mentions? I can't seem to find anything on the subject in the Scratch website's "Research" section (https://scratch.mit.edu/info/research/), and in their early papers they simply list it as a "core feature" rather than explaining why they use blocks in the first place.
Re: How computer programming languages for kids have evolved and where they're going
#3Why aren't kids able to read text written in rows like everyone else? Programming languages just for kids seems mostly like a way to limit them.
Re: How computer programming languages for kids have evolved and where they're going
#4[Follow up read] Why developers never use state machine:
http://www.skorks.com/2011/09/why-developers-never-use-state...
Re: How computer programming languages for kids have evolved and where they're going
#5I've always been suspicious of the looks-like-an-animal-with-a-name-and-a-smiley-face-I'm-a-grown-up-and-this-is-what-kids-like approach. I remember one of the coolest things about the apple II was that you could 'poke' the right memory address and get the speaker to click. That was magic when I was 12 and it didn't need a friendly name and a stupid grin. Until they're old enough for K&R (12?, 13?, 14?), maybe they should do something else... or maybe anything else...
Re: How computer programming languages for kids have evolved and where they're going
#6Does anyone know of any published research on the efficacy of this "block based programming" standard the author mentions? I can't seem to find anything on the subject in the Scratch website's "Research" section ( https://scratch.mit.edu/info/research/ ), and in their early papers they simply list it as a "core feature" rather than explaining why they use blocks in the first place.
I've been a CodeDojo and Scratch mentor for a few years and, although I haven't read much of the research, block-based programming fills a great niche for kids that know how to read, but have a hard time typing. Typing and syntax issues hinder the experience for very young children learning to code.
Scratch allows children to learn computational thinking concepts through a creative computing experience. Keeping it simple and focusing on the creative aspect of programming is a major emphasis of Mr. Resnick's team at the Lifelong Kindergarten Group.
The kids that choose to continue with programming eventually reach a wall with Scratch, where the block-based aspect breaks down. At which point they are ready for syntax-based languages. However, it's amazing how complex some of the featured projects are on the Scratch website with regards to both art and logic.
Re: How computer programming languages for kids have evolved and where they're going
#7Does anyone know of any published research on the efficacy of this "block based programming" standard the author mentions? I can't seem to find anything on the subject in the Scratch website's "Research" section ( https://scratch.mit.edu/info/research/ ), and in their early papers they simply list it as a "core feature" rather than explaining why they use blocks in the first place.
In my experience in using this with my Daughter (age 7) I think the main efficacy of blocks comes from making it easier for kids who don't know how to type to use the basic programming concepts we are used to (nesting, loops, conditionals). What other aspects of efficacy are you thinking should be considered?
Re: How computer programming languages for kids have evolved and where they're going
#8[Follow up read] Why developers never use state machine: http://www.skorks.com/2011/09/why-developers-never-use-state...
I almost always use state machines.
Re: How computer programming languages for kids have evolved and where they're going
#9Why aren't kids able to read text written in rows like everyone else? Programming languages just for kids seems mostly like a way to limit them.
I don't think it's about being able to read text written in rows, although if you can't see that kids aren't particularly good at that initially, then you mustn't have spent much time with kids. (Hint, they learn to "read" with picture books and then books with like 5 words on a page.)
The same reason they learn to ride a bike on one with 12 inch wheels instead of 700c. Or cook using recipes with 3 ingredients.
Simplified versions for learning are a good thing.
First they grasp the basics using something simple, then they push the boundaries of that simplified version, and then they extend to the next step up.
The same way I learn at 33 years old, by the way.
Re: How computer programming languages for kids have evolved and where they're going
#10Does anyone know of any published research on the efficacy of this "block based programming" standard the author mentions? I can't seem to find anything on the subject in the Scratch website's "Research" section ( https://scratch.mit.edu/info/research/ ), and in their early papers they simply list it as a "core feature" rather than explaining why they use blocks in the first place.
There seem to be a few studies like this that have evaluated scratch over the course of 10 classes, but they've been largely inconclusive beyond the "general enjoyment" factor - http://scratched.gse.harvard.edu/sites/default/files/wilson-...