News for hackers. Stuff that matters.
Re:Let's make a "type the code listings" book for kids. by stcredzero on Monday April 19, 2010 @12:37PM (#1277109)
Why not an environment where you're just a click or two away from browsing (editing, changing, and running) the source code of everything?

http://www.squeak.org

Edit: To encourage kids to tweak and program, make the source easy to get to and a breeze to modify. Forcing them to type The whole program to do this strikes me as a bit indirect. We did it in the early 80's because we had to. Often, there was no other way to get your hands on that particular program. Today's environment is vastly different.

Re:Let's make a "type the code listings" book for kids. by tlb on Monday April 19, 2010 @03:40PM (#1277635)
I think you learn something by typing it in that you don't by scanning code on the screen. I learned a lot by typing in Applesoft Basic programs when I was 10. It's like the difference between learning a language by actively trying to speak it, vs. just reading.
Re:Let's make a "type the code listings" book for kids. by stcredzero on Monday April 19, 2010 @04:43PM (#1277792)
That's Not the point. It's not the reading, or the typing in that's the key. It was the tweaking! Typing in source code gives you the freedom to tweak because, dammit, you typed that in in the first place! But being able to instantly change source and see the results of it instantly in the running system -- this is a much more immediate way of encouraging tweaking.

I'm saying, so long as you want to encourage X, why not directly take the steps to encourage X?

Re:Let's make a "type the code listings" book for kids. by dagw on Monday April 19, 2010 @06:04PM (#1277994)
I haven't thought about it for ages, but now looking back on those days, it seems the thing I really learnt was debugging. I basically never got those programs working on the first try and trying to work out exactly what mistake I made was probably at least as educational as modifying the code to make it do new things.

That being said, I'm not entirely convinced this is still a good way to teach coding.

Re:Let's make a "type the code listings" book for kids. by bphogan on Monday April 19, 2010 @05:02PM (#1277844)
I don't think you're wrong. But I think we need the examples before we can prove you're right. Nothing prevents anyone from taking this code and building a lab out of it as a secondary method of learning.

Of course, you're perfectly free to set up your own project using Squeak. I bet you'd get a lot of people onboard with that. Then you can prove me wrong :)

Re:Let's make a "type the code listings" book for kids. by stcredzero on Monday April 19, 2010 @05:40PM (#1277926)
Again you're not quite understanding the point. Squeak already is a massive project of the kind you're referring to, but substituting instant source access/change/immediate feedback for having kids type in code.
Re:Let's make a "type the code listings" book for kids. by bphogan on Monday April 19, 2010 @12:49PM (#1277155)
Nothing wrong with that, and it could be a valuable project. With a book, we have more options. We have the code, we can send it out as a web page, we could have it printed as a textbook, we could even build some kind of interactive system to run it.

But first we need the code. Then we can figure out what to do with it :)

Re:Let's make a "type the code listings" book for kids. by stcredzero on Monday April 19, 2010 @01:03PM (#1277216)
I think you missed the point. Squeak is an environment where the source code of everything is just a few clicks away. Everything is easily tweakable by design.

I think that's even more accessible and tweakable than a system where the source code is 100's of keypresses away.

Re:Let's make a "type the code listings" book for kids. by bphogan on Monday April 19, 2010 @01:06PM (#1277231)
I think looking at source code is passive. Having to type it in is not. There's something... different about typing it in, learning by doing. We all spend our days copying and pasting. What was neat about the code books was that you couldn't cheat. Typing each keypress to understand how a loop worked was very helpful. The reward for all of that was that you could play the game. That's why they're not supposed to be long, or overly complex in the beginning.

Of course, everyone learns differently. I could certainly be way off base. But I bet most people who actually did those code listings would agree that there's a certain value there that's very hard to reproduce with view source and cut+paste.

Re:Let's make a "type the code listings" book for kids. by stcredzero on Monday April 19, 2010 @01:30PM (#1277307)
I think looking at source code is passive. Having to type it in is not. There's something... different about typing it in, learning by doing.

Yes, but instead of getting kids into doing by forcing them to type, I think it's much better to just make the source accessible and encourage them to tweak.

You may not know this about Smalltalk, but not only can you browse the source code of everything quickly, you can change it and have those changes active instantly on a key press. In fact, the whole thing was specifically designed as a digital Montessori toy for kids.

I think forcing today's kids to type in source code will just be seen as unnecessary drudgery. If doing is what we want to encourage, why not just make it easy to do and provide some guidance in that direction?

Re:Let's make a "type the code listings" book for kids. by raimondious on Monday April 19, 2010 @01:11PM (#1277250)
I agree — I like to learn new programming languages from books precisely because I have to type in any tutorial material by hand.

Thanks for starting this — all this talk of closed systems keeping kids from playing with programming, and whether video games/programming was art or not was distressing.