5 ms·
I like Swift as a language, but I have my doubts as to its suitability as a first-time programming language for children. It contains a whole lot of industry-st
by kibwen 10y ago
I like Swift as a language, but I have my doubts as to its suitability as a first-time programming language for children. It contains a whole lot of industry-standard jargon that we as practiced software developers don't think twice about, and will have to be explained. Like, what the heck is a "string", and why is it called that? What is this weird vertical character that I've never seen before (and how do I even begin to type it? is it an emoji?) and why do two of them next to each other mean "or"?
I don't doubt that kids are smart enough to wade through it all, but if you put enough obstacles in their path then they're going to wander off and do something more interesting. It also raises the question of whether you're teaching kids programming for the sake of programming (in which case you'd rather use any of the myriad languages that have been designed for young children), or if you're teaching kids programming for the sake of helping them solve some problem or achieve some task (in which case you'd probably pick a language with a more specific focus), or whether you're just teaching them programming just for the sake of adding to the ranks of the software industry ten years from now.
- stormbrew 10y agoIt seems to do a lot of holding your hand through all those things, but I've always been very skeptical of the idea that the things you listed are real barriers to understanding. The fact is that those are surface details that are far less likely to tank your understanding of what's going on than basic problems understanding logic and execution flow. When I see beginners struggle, it's not because they've been given sigils they don't understand (it'd be almost impossible not to: even using words like 'or' and 'and' carry various secondary meanings unique to programming and/or formal logic), but because they're having trouble building a meaningful mental model of the execution of the program. Live visualizations help a lot with that fundamental problem. From there you can learn the details. I think this way around is far more successful. Fundamentally, this argument's been had over and over and over again, and in the end the languages people learn are the languages people use. BASIC is probably the most successful 'learning language' ever, but it became successful in environments where people were using it for productive work (as the boot rom environment on older computers and with visual basic). Likewise, Pascal only became popular when it became possible to use it for productive work (thanks to Borland Pascal and later Delphi). Otherwise, allegedly 'easier to learn' languages lose every time to the ones people can move from success to success all the way from learning to productive work.
- kibwen 10y ago> basic problems understanding logic and execution flow I don't disagree with this. My point is that layers of obfuscation on top of the really difficult bits only make it harder to devote attention to the difficult bits. Beyond a certain threshold, beginners throw up their hands and walk away, especially if they're motivated only by curiosity (which seems to be the target audience of this app). I know I reached this stage as a teenager when trying to learn C++ (because I wanted to make video games, you see, and everyone told me this was the only language to use), and trying to perform even the simplest operations was piled under layers and layers of seemingly-arbitrary nonsense. I gave up and didn't touch C++ again until after college. In all, I think there's survivorship bias at work here. We say that these things aren't a problem, that they aren't barriers to understanding, but the only people here in this discussion are the ones who haven't already become discouraged. It's no wonder when things are seen as not-a-problem by people who didn't have a problem with them.
- stormbrew 10y agoI'm not sure appealing to survivorship bias is useful here, since presumably you are also a survivor and just as subject to it. But my argument was based on my observations of other people trying to learn. My experience learning was quite different from most that I've observed, and my observation has actually been that the way I learned is the one that works for fewer people. This is an area of interest for me, so I take opportunities to see how people learn as much as I can. If anything, the better argument against what I'm saying is that it's just anecdata, which is true. I'd welcome research to prove this one way or another, though. Tools like this are quite unlike what I had available to me, and I think they are a much bigger step to creating learning environments for real computing than trying to shoehorn natural language into a box it just doesn't fit. We have been down that road so many times and it never works out the way proponents suggest it should.
- Cookingboy 10y agoI think you are grossly underestimating young people. Learning || to mean OR or String to mean "a series of characters" is by no means beyond the capability of kids.
- kibwen 10y agoI explicitly said in my comment that I am confident that kids are capable of learning these concepts. You seem to be asserting that an abundance of jargon, unfamiliar symbols, and unintuitive names are no obstacle to people learning to program, but sit a first-timer down with Befunge or Malebolge and we'll see how far they get. :) User interface matters, and it especially matters to people who have not yet internalized all the latent, lingering idiosyncrasies of programming in general.
- Apocryphon 10y agoWhat are the other major first languages for kids? I'm not sure if Swift is worse than JavaScript.
- Clubber 10y agoI think the first programming I did was Turtle Logo, or Apple Logo or whatever it was called. Traditionally it's been Pascal and Basic, but I think those aren't used much anymore. I learned Commodore Basic first then Pascal in High School and CS1 in college.
- bpyne 10y agoKids need to start with small, quick successes before they are willing to invest more time. The Playground weighs in Swift's favor because they can get immediate feedback. As for the language itself, it seems to have decent type-inferencing. So, kids won't get bogged down on a compiler not liking "String" vs. "string". To really capture kids' imaginations, Apple needs to visual and auditory libraries loaded and ready to go in the Playground. Kids will immediate want to build something graphical or auditory. It's an interesting experiment.
- empath75 10y agoTo be honest, I think that A) Literally everything is new to a kid, and if they can figure out how to play pokemon and minecraft, they can figure out what '||' means. B) Why teach them one way to do things and force them to relearn it a few years later?
- kibwen 10y ago> B) Why teach them one way to do things and force them > to relearn it a few years later? Who says anyone's being forced to relearn anything? My initial progression of languages went QuickBASIC -> Visual Basic -> Java, and despite the fact that Java is nothing like QuickBASIC the concepts helped me immensely in powering through Java's intimidating learning curve (i.e. "just type `public static class Hello { public static void main(String[] args) { system.out.println("Hello"); } }` for now (and for god's sake, make sure the file name is Hello.java), you'll understand what all that means in about six months or so"). It's easy to forget that our first exposure to programming involves a lot of fundamental concepts that are wholly incidental to the semantics of whatever language we're using. Trivial stuff like case sensitivity of identifiers (quite surprising to an enormous number of first-time programmers) as well as highly non-trivial stuff like setting up your programming environment and teaching people how to invoke the compiler/interpreter. Making the language itself small and intuitive, even if limited, goes a long way towards giving students a stone to cling to in the rushing river of unfamiliar concepts that they're being exposed to.
- kartickv 10y agoRegarding B, because starting them with a complex language may make many of them give up on programming completely.
- GuiA 10y agoI've taught programming to thousands of children, teenagers, and adults for a bit over a decade now (not exagerating, I've been through the exercise of estimating, for each of my gigs, how many students I've interacted with directly), in a wide variety of contexts (summer camps, bootcamps, middle schools, undergraduate classes, etc.), using a wide variety of languages (C, Python, Scratch, Ruby, PHP,...). The things you quote are typically not much of an issue. Once you tell students what a string is, or you show them how to type | or ^ or & or whatever weird symbol, they typically remember it (of course, you'll get some "oh yeah I need to use that weird squiggly thing here, how do I type that again?" - and as a fun tidbit, students in 2016 have no problem remembering and typing the # symbol (aka a "hashtag") ). The bigger issues come from more macro level things, like understanding that the code gets executed on a line by line basis and can't "read the future" (i.e. you can't use a variable if it's only declared 10 lines later), what scoping is, how to combine conditions together to make a loop that does what you want it to do, and so on.
- kartickv 10y agoHere's an attempt at defining a simple, minimal programming language, which would be useful to kids and adults choosing to learn programming and people looking for something simpler than the popular languages today: http://kartickv.tumblr.com/post/142934120532/why-arent-there-simple-programming-languages http://kartickv.tumblr.com/post/142934120532/why-arent-there...