creating a framework to teach MOO

[basil60]

A recent thread prompted this post, and it's been a while coming, as I sort stuff out in my head.

Some background:

There's a big push around the world to get kids programming again. And adults appear to be jumping on the bandwagon too!!

I've been dabbling with teaching kids at school programming in enCore MOO. Most have no background in either MOO or programming, but are keen.

Those who've seen my posts on this list know I'm not much of a programmer (in MOO) or the other languages I have to teach - I'm a Jack of all trades - Master of none.

But I'd like to find a process that allows kids to move from basic programming constructs to useful programming. That's where I see the MOO being out on it's own - with imagination, you can programme anything.

I've started with some basics like strings, sequence, moving onto iteration, but mostly using materials I've adapted from other lessons I've done (ie JavaScript or ActionScript). I've attached some of the stuff I'm talking about it a text file.

I'm really seeking advice on how to go from the theoretical to useful programming in a MOO (ie to do really useful stuff - stuff that will engage and really keep them going with a passion for a programming).

I've used VB, JavaScript, ActionScript, Java, Basic and others, and never quite got as excited as I have with MOO. While I haven't created anything especially worthwhile, I'd like to be able to ignite a passion in these kids, and I'm convinced MOO is the way. But the framework to get there has to be right.

I'd appreciate any positive advice.

[Todd Sundsted]

Are you interested in teaching students about programming, or teaching
them to be programmers?

In the latter case, I've found that more than understanding syntax is
necessary to be a good programmer. A few things to think about...
They will need to develop skill in breaking problems into smaller
parts, and then assembling solutions to each part back into a working
whole. Consider teaching that specific skill (which could be broadly
useful in life, IMHO) as part to the curriculum. They will need to
learn how dig into a complex system to find the piece that is not
working correctly (AKA debugging -- half of my time _at least_ is
spent debugging). Consider giving them non-working code, and asking
them to fix and/or improve it.

Todd

>  moo_lessons.txt
> 3KViewDownload

[Paul Rayner]

Thanks Todd

 

I guess I'd never differentiated the two. Interesting thought!  I guess it is the latter - because many of the kids won't go on to be programmers. But, as you say, it's really aprt of life. As Rushkoff would say "Programme - or be programmed"!

 

Personally. I find the language specific syntax the most difficult. The bits you have to trawl through the manual to find, and then work out how they are used.

I thought the group might have had suggestions as to how they had made the progression from the simple to the more complex in their moo careers.

 

Paul

--
You received this message because you are subscribed to the Google Groups "MOO Talk" group.

To post to this group, send email to MOO-...@googlegroups.com.
To unsubscribe from this group, send email to MOO-talk+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/MOO-talk?hl=en.

[Todd Sundsted]

(My two cents, then...)  For me, becoming a better programmer (moo or
otherwise) went hand-in-hand with attempting more ambitious projects.
 Each project improved existing skills and forced me to learn new
skills.  Not so different from learning to write or to play a musical
instrument.  Can you encapsulate the learning in the context of a
individual or group project? In a VR like LambdaMOO, perhaps teams of
students could work to create team rooms full of interactive objects
as part of the course.

Todd

On May 21, 5:24 pm, Paul Rayner <prayner.ba...@gmail.com> wrote:
> Thanks Todd
>
> I guess I'd never differentiated the two. Interesting thought!  I guess it
> is the latter - because many of the kids won't go on to be programmers.
> But, as you say, it's really aprt of life. As Rushkoff would say "Programme
> - or be programmed"!
>
> Personally. I find the language specific syntax the most difficult. The
> bits you have to trawl through the manual to find, and then work out how
> they are used.
> I thought the group might have had suggestions as to how they had made the
> progression from the simple to the more complex in their moo careers.
>
> Paul
>

[Stephen Gigante]

My personal approach has always been to give them faulty code, and tell them "Here's the code.  Here's what it should do when you fix the errors, and here's a list of things you could do with it once you fix it up."

Having a few possible applications for the code once they're done debugging it is usually a good motivator, and gives them a good base to build future ideas from.

 - Stephen