I mentioned in a previous blog post the nice summary article that Audrey Watters wrote (linked below) about Learning to Code trends in
educational technology in 2012, when I critiqued Jeff Atwood’s position on not learning to code. Audrey does an excellent job of describing the big trends in learning to code this last year, from Code Academy to Bret Victor and Khan Academy and MOOCs. But the part that I liked the best was where she identified the problem that cool technology and badges won’t solve: culture and pedagogy. This is a problem. A big problem. A problem that an interactive JavaScript lesson with badges won’t solve.Two organizations — Black Girls Code and Code Now — did hold successful Kick starter campaigns this year to help “change the ratio” and give young kids of color and young girls opportunities to
learn programming. And the Irish non-profit Coder Dojo also ventured state-side in 2012, helping expand after school opportunities for kids interested in hacking. The Maker Movement another key ed-tech trend this year is also opening doors for folks to play and experiment with technologies. And yet, despite all the hype and hullabaloo from online learning start ups and their marketing campaigns that now “everyone can learn to code,” its clear there are still plenty of problems with the culture and the pedagogy surrounding computer science education.
via Top Ed-Tech Trends of 2012: Learning to Code | Inside Higher Ed. We still do need new programming languages whose design is informed by how humans work and learn. We still do need new learning technologies that can help us provide the right learning opportunities for individual student’s needs and can provide access to those who might not otherwise get the opportunity. But those needs are swamped by culture and pedagogy.What do I mean by culture and pedagogy?Culture: Betsy diSalvo’s work on Glitch is a great example of considering culture in computing education. I’ve written about her work before — that she engaged a couple dozen African-American teen men in computing, by hiring them to be video game testers, and the majority of those students went on to
post-secondary education in computing. I’ve talked with Betsy several times about how and why that worked. The number one reason why it worked: Betsy spent the time to understand the African-American teen men’s values, their culture, what they thought was important. She engaged in an iterative design process with groups of teen men to figure out what would most appeal to them, how she could re frame computing into something that they would engage with. Betsy taught coding — but in a different way, in a different context, with different values, where the way, context, and values were specifically tuned to her audience. Is it worth that effort? Yeah, because it’s about
making a computing that appeals to these other audiences.
Pedagogy: A lot of my work these days is about pedagogy. I use peer instruction in my classrooms, and try out worked examples in various ways. In our research, we use sub goal labels to improve our instructional materials. These things really work.Let me give you an example with graphs that weren't in Lauren Margelieux’s paper, but are in the talk slides that she made for me. As you may recall, we had two sets of instructional materials: A set of nice videos and text descriptions that Barbara Ericsson built, and a similar set with sub goal labels inserted. We found that the sub goal labelled instruction led to better performance (faster and more correct) immediately after instruction, more retention (better performance a week later), and better performance on a transfer task (got more done on a new app that the students had never seen before). But I hadn't shown you before just how enormous was the gap between the sub goal labelled group and the conventional group on the transfer task.
Part of the transfer task involved defining a variable in App Inventor — don’t just grab a component, but define a variable to represent that component. The subgoal label group did that more often. ALOT more often.
Lauren also noticed that the conventional group tended to “thrash,” to pull out more blocks in App Inventor than they actually needed. The correlation between number of blocks drawn out and correctness was r = -.349 — you are less likely to be correct (by a large amount) if you pull out extra blocks. Here’s the graph of number of blocks pulled out by each group.
These aren’t small differences! These are huge differences from a surprisingly small difference between the instructional materials. Improving our pedagogy could have a huge impact. I agree with Audrey: Culture and pedagogy are two of the bigger issues in learning to code.
Deepa Singh
Business Developer
Email Id:-deepa.singh@soarlogic.com
