2 ms·
Fair enough. I still disagree with your conclusion. Text isn't keeping kids from coding, throwing them at Swift's text (in your case) was. A simpler and more fo
by Jtsummers 9y ago
Fair enough. I still disagree with your conclusion. Text isn't keeping kids from coding, throwing them at Swift's text (in your case) was. A simpler and more forgiving syntax, or a UI (a very capable IDE in this case) that walks them through the syntax (showing them only the valid options at any given point) since you chose a relatively complex syntax would also have helped. You achieved that via pictographs transition via pictographs, which ought to be effective (you won't be changing the rules of the game on them, from their perspective, just the notation used).
Pictographs are useful, and effective. I won't deny that. But kids can, and have, learned to code with textual languages when those languages were more effectively chosen and developed for the task of teaching kids. It's unreasonable to make such a strong claim.
We could make the same claim about math and kids (Notation is Keeping Kids from Mathing!), and it would be superficially true, if you started kids off with a notation like geometric algebra (bi-vectors, tri-vectors, multi-vectors, oh my!), instead of arithmetic.
- dyarosla 9y agoThe point I want to stress is that text is keeping kids from coding. Like I said, even with punctuation-less text, the game was deemed difficult. Simpler and forgiving syntax simply would not help. The IDE in the game is actually extremely forgiving and could just as well walk players through the syntax, but interest levels then drop off. This is the difference between in theory and in practice. Yes there are kids that had no problem with text or without text. Of course kids can and have learned to code with textual languages. Same with math. The main idea here is that you can get an even larger population of kids doing math and coding, and engaging, by adopting pictographs first. As demonstrated in DragonBox. As seen in our own testing.