Slashdot Mirror
Teaching Programming Now Emphasizes Sharing
An anonymous reader writes "The NY Times explores some of the best ways to teach kids and finds that some of the new tools are encouraging the kids to share their work with each other. One teacher first tried to keep the kids quiet and staring at their own monitors but found it was better to let them copy each other. He calls MIT's Scratch a 'gateway' tool. Then the article points out that programming Blender with Python is not as hard to pick up as your grandparent's programming languages — and kids today are learning them in a few months." The Wikipedia entry on Scratch is worth reading, too.
The summary makes it sound like these kids are being encouraged to cheat off one another. The actual article just says that they're looking at each others' work to build on one another to make more complex programs. That pretty much describes what any good programmer does. Unless you live in a bubble building all small projects solo, you're always going to be working together on a project with other programmers and designers. And even if you live in a bubble, you had to learn coding from SOMEWHERE. You look at code in a book or on a website, you learn how it works, you start using it and adapting it in your own projects. That's just learning.
I, for one, say "Huzzah!" for these kids. If they keep at it and get their CS degrees, they'll have a great future working for $3-an-hour in India someday.
Wait, that sounds cynical. I meant $4-an-hour.
Oh, and I've found Alice to be a great teaching tool for kids too. It teaches programming principles in a way that's a little more exciting for beginners than having to learn Commodore 64 PEEK and POKE coding (the way some of us came up).
SJW: Someone who has run out of real oppression, and has to fake it.
In high school my math teacher organised us into pairs and encouraged us to work together on the problems. It's can be very enlightening to see a situation from someone elses point of view. And teamwork is also a skill that has to be learned, preferably in school.
If your students are motivated by "building cool stuff", sharing is great - they are trying to add the elements they find into their own designs. However, if your students are motivated buy "getting the passing grade", then sharing may become copy-pasting, and they will not retain any knowledge of the process. In real life, students are motivated, to a different degree, by building cool stuff, grades, and a host of other factors. My policy up to date has been "ideas sharing is fine, peering at screens and finding out how others did things is fine, but if I find evindence of significant copy-pasting, you will get a stern warning and/or a some sort of discipline". Works fine with undergrads learning compsci, especially once they learn that our in-house copy-pasting detection system is quite accurate at finding cases of badly-disguised cut&paste.
I am even going one step further, and *making* my students review each other's code (they get good grades for writing good reviews, not for receiving them, and reviews are anonymous, so there should be little incentive to 'cheat'). I find that far too many students are not exposed to a) the potential beauty and simplicity of good code vs. b) the horror that bad coding is to the unwary mind.
Does anyone know good systems to automate this peer-review for undergrad coding exercises?
It'll teach the kids to write the most simple programs - but once they need to use a real programming language, they need to unlearn Scartch.
I've taught Scratch to kids before, though only briefly. None of the class picked up much on their own, so it's no replacement for good tuition.
In high school my math teacher organised us into pairs and encouraged us to work together on the problems. It's can be very enlightening to see a situation from someone elses point of view. And teamwork is also a skill that has to be learned, preferably in school.
That's annoying as hell for the smart kids paired with kids who just don't get it. Being one of those kids that didn't like "showing my work", I would have spent 50 minutes of a 60 minute class teaching my partner how I got the solutions. Conversely, there were kids smarter than me, and I didn't want them giving away the answer before I'd figured it out on my own. People need to learn how to solve problems on their own. In my humble opinion, math is only a team sport for anyone going above Calculus. I don't believe in that one for all, all for one junk in school. Let's save the teamwork for Phys-Ed.
Sounds like a great way for the teacher to make other students do the job of the teacher. I certainly don't want my son going to school and spending the majority of his time teaching rather than learning something new under some false assumption that they can all be winners. As the kid who always held the class record for math speed tests in elementary school, its a shitty teacher that would make that me spend most of my time helping other students on rudimentary problems when I could have instead moved on to something more challenging.
If that kid's parents want to pay me for after school tutoring, that's fine! Heck, I paid another student for music lessons over a summer in high school. He was a first chair, and I was 5th. My money resulted in him being paid for a valuable service that helped me make second chair the next year. But should he become the instructor of all the kids below him? Hell no, he was allowed to shine on his own. This guy went on with a music scholarship, and the rest of us just have band camp memories. Why hold him back? Why hold back excellence? I can only imagine someone like modern Einstein in high school wasting time trying to explain chemical bonding to a kid who will grow up to flip burgers. That's a far out analogy, but it highlights the problem, at least until later years of college where classes aren't just large groups of kids lumped together not by knowledge, but simply by age and geography.
I want kids to go to school to learn, not teach remedial topics to their classmates.
I8-D
Reading (and figuring out) someone else's code is one of the best ways to learn to program. It also teaches the value of commenting your code and making it understandable and maintainable by others.
As for the "cheating" aspect:
1. In the real world, programmers "cheat" by sharing code to get the job done with the least effort.
2. Switch up the groups after every assignment so the learn to work with different people, you'll see a pattern in who is productive and who is a slacker.
3. In the later phases, switch up the groups in the middle of the assignment, just like a real workplace.
make imaginary.friends COUNT=100 VISIBLE=false