I had an interesting semester this term. It wasn't easy, but I learned a lot - more than I bargained for in fact. I'm going to break it out into two posts because I had very different experiences in my two classes.
I'll start with Java programming which was an online class. I'm a believer that online learning can work when done right. I've taken three online classes in this program so far. One was great, two were not. I'm sure it's just a coincidence, but the class that was great was in Moodle, the other two were both in Blackboard - I'm just sayin!
The good experience was a class in Moodle about Online Learning. In that class there was a big emphasis set on discussions and participation at the outset, and I think it set the tone for the rest of the semester. There were a lot of great readings in that course, but what stood out even more were the discussions. I remember my greatest challenge that semester was trying to manage my time, I was spending too much of it in the discussion forums keeping up with, and contributing to, really interesting conversations that were going on. It was a bit all consuming, but in the best possible way.
The other two classes - Java I, and Cognition and Learning - were more solitary classes. There was an attempt to prompt discussion, but it didn't take. My suspicion is that it was due partly to the implementation of the class - directives given in terms of expectations of contribution - and partly due to the discussion forum functionality. In Blackboard it seemed a bit clunky to me, and it was more robust in Moodle.
While I'm a believer in online learning in general, the online class I took this semester was not a good experience for me. I had no prior programming experience and by surveying the student profiles, it seemed that about half of us did and half did not. Interestingly, the class started with about 24 students and by week two we were down to 12. My father who is a computer science professor said a high drop out rate in programming classes is typical. [Insert angst about STEM skills here].
In terms of learning how to program, reading the text book and watching voice thread videos didn't cut it for me. I started looking at youtube to find videos that might help explain these new concepts to me, I went to Barnes and Noble to buy every book I could find - particularly those with "For Dummies" in the title. Ultimately, I turned to my father for tutoring.
This was not the first time I had asked him for extra help. He helped me with math all through school (I always knew he knew more than my teachers) and he gave me all the interesting back stories that they don't tell you in the history books. When I complained that I'd never make it through my Melville course in college, he had me send him the reading assignments, he got the books and we had a weekly book group by phone. :)
Interestingly, these weekly tutoring sessions in Java brought me right back to childhood math. The pang of panic when asked a question for which I was expected to have some semblance of a reasonable reply. The deer in the headlights look that I knew was on my face but I couldn't erase. Oh the horror! I tried to breath deeply, tried not to panic. It wasn't easy and it wasn't comfortable. I thought to myself that I should try to embrace the uncomfortable feeling and use it to remember how it feels for my kids and other kids when they feel overly challenged or taxed.
I got through it - but only because of the weekly tutoring sessions. I was left thinking about my other classmates who also didn't have any programming experience and who most likely did not have someone like my dad around to help them. How did they fare? I have to admit that I couldn't help but think - how is it that here, in an educational program, this is the best that can be done to teach programming? Especially in light of how much in need we are to develop these skills, and foster more students to start and complete STEM programs. We have to do better than this.
Wednesday, May 11, 2011
Tuesday, April 12, 2011
Video games in education
Recently we were asked in class to consider the role of video games in education, a really interesting topic, and a very popular one! I think there is tremendous possibility in this area, but I also think that there is so much for us to figure out in order to do it right.
A classmate used the analogy that some games are just like chocolate covered broccoli. Game design is so important. The barrier approach - do these drill and kill style problems in order to go do this fun game - won't cut it. The learning and the game play have to be engrained and purposeful.
Some of my favorite research articles are by Squire and Barab and are related to this topic. You can find Electromagnetic Supercharged! and History Replayed on Google Scholar. One thing that both their studies found was that while it was assumed that students would naturally embrace game play, some students pushed back and were uncomfortable with the idea. Some students asked - why are we doing this - and others made comments like - we're not used to talking in class. What I took from those articles, in addition to the fact that there is so much potential to using games in education, is that the role of classroom culture is a huge factor in the success or failure of these programs. We need to better understand how to create an environment or community where this type of learning can thrive.
Last but not least, my favorite topic: how do we measure success? That kids are engaged in a game isn't enough. What are they learning by virtue of the experience. How can we evaluate what learning is happening and to what degree. How do we decide what games to invest time and energy into and which games don't measure up - what is the yard stick?
These are the really interesting questions that I see surrounding the issue. Like I said, I see huge value in using video games in education, but also see a lot of thinking and planning that needs to happen in order to be able to do it right.
A classmate used the analogy that some games are just like chocolate covered broccoli. Game design is so important. The barrier approach - do these drill and kill style problems in order to go do this fun game - won't cut it. The learning and the game play have to be engrained and purposeful.
Some of my favorite research articles are by Squire and Barab and are related to this topic. You can find Electromagnetic Supercharged! and History Replayed on Google Scholar. One thing that both their studies found was that while it was assumed that students would naturally embrace game play, some students pushed back and were uncomfortable with the idea. Some students asked - why are we doing this - and others made comments like - we're not used to talking in class. What I took from those articles, in addition to the fact that there is so much potential to using games in education, is that the role of classroom culture is a huge factor in the success or failure of these programs. We need to better understand how to create an environment or community where this type of learning can thrive.
Last but not least, my favorite topic: how do we measure success? That kids are engaged in a game isn't enough. What are they learning by virtue of the experience. How can we evaluate what learning is happening and to what degree. How do we decide what games to invest time and energy into and which games don't measure up - what is the yard stick?
These are the really interesting questions that I see surrounding the issue. Like I said, I see huge value in using video games in education, but also see a lot of thinking and planning that needs to happen in order to be able to do it right.
Is programming the new literacy?
There have been a couple interesting articles recently on the current and future importance of programming skills.
Clive Thompson had an article in Wired a few months ago called coding for the masses:
http://www.wired.com/magazine/2010/11/st_thompson_wereallcoders/
Marc Prensky also wrote an article called Programming is the new literacy:
http://www.edutopia.org/programming-the-new-literacy
Thompson's take is that software affects almost everything we do, and therefore more of us need to become acquainted with the field of programming. In addition he says that understanding programming changes the way you look at things. It makes you realize that every problem is comprised of many smaller problems. This understanding of how to approach problem solving might enable people who use software to be less passive users ( accepting whatever a software company builds and delivers) and more of an educated consumer (it's not impossible to change this, and it's not even hard to do, so fix it to enable users to do X). The book Program or be Programmed by Douglas Rushkoff is cited in the Wired article, I'm planning on checking it out, I'll let you know if it's good.
The Prensky article argues that so many things we do in everyday life qualify as programming something. From setting up your universal remote to changing your settings in facebook or blogger. I do not believe that the fact that I change settings in a software I use makes me a programmer. I don't even necessarily agree that everyone will *need* to be able to program, say in C++ or Java. I do, however, think that there will be more instances where the barrier to entry for programming skills are lessened, and things like scratch, alice, flash, even android's app inventor are early examples of what I think will be an ongoing trend.
What I think is at the heart of the issue in this programming literacy conversation is to achieve agility in learning - to realize and be comfortable with the fact that for the rest of your life you will continually be learning new, and sometimes hard, things. I don't think the key is whether someone can program in one language or another per se, but that they have the attitude to roll up their sleeves and get dirty learning something new, even if it's hard and/or scary at first, for the sake of being able to do more things and be more of an active empowered participant, and less a passive receiver. Maybe we should design some sort of game to promote programmatic and hacker thinking in kids!
Even if someone does become proficient in one programming language, new languages come along and other languages fall off. I think it is the mindset to continually learn and challenge yourself that will be increasingly critical in our world.
Clive Thompson had an article in Wired a few months ago called coding for the masses:
http://www.wired.com/magazine/2010/11/st_thompson_wereallcoders/
Marc Prensky also wrote an article called Programming is the new literacy:
http://www.edutopia.org/programming-the-new-literacy
Thompson's take is that software affects almost everything we do, and therefore more of us need to become acquainted with the field of programming. In addition he says that understanding programming changes the way you look at things. It makes you realize that every problem is comprised of many smaller problems. This understanding of how to approach problem solving might enable people who use software to be less passive users ( accepting whatever a software company builds and delivers) and more of an educated consumer (it's not impossible to change this, and it's not even hard to do, so fix it to enable users to do X). The book Program or be Programmed by Douglas Rushkoff is cited in the Wired article, I'm planning on checking it out, I'll let you know if it's good.
The Prensky article argues that so many things we do in everyday life qualify as programming something. From setting up your universal remote to changing your settings in facebook or blogger. I do not believe that the fact that I change settings in a software I use makes me a programmer. I don't even necessarily agree that everyone will *need* to be able to program, say in C++ or Java. I do, however, think that there will be more instances where the barrier to entry for programming skills are lessened, and things like scratch, alice, flash, even android's app inventor are early examples of what I think will be an ongoing trend.
What I think is at the heart of the issue in this programming literacy conversation is to achieve agility in learning - to realize and be comfortable with the fact that for the rest of your life you will continually be learning new, and sometimes hard, things. I don't think the key is whether someone can program in one language or another per se, but that they have the attitude to roll up their sleeves and get dirty learning something new, even if it's hard and/or scary at first, for the sake of being able to do more things and be more of an active empowered participant, and less a passive receiver. Maybe we should design some sort of game to promote programmatic and hacker thinking in kids!
Even if someone does become proficient in one programming language, new languages come along and other languages fall off. I think it is the mindset to continually learn and challenge yourself that will be increasingly critical in our world.
Monday, September 27, 2010
Mindtools
Originally when I heard the term "mindtools" I associated it with concept maps or schemas, like the kind you would create using webspiration. I didn't see how Excel could be considered a mindtool. Having read the Jonassen chapter on mindtools I realize that anything that forces you to reflect on and organize your thinking is a mindtool. Looking at it from that perspective, I can absolutely see how excel could be considered a mindtool in that you are forced to consider discrete pieces of information, how to categorize them, organize them, and how best to create visualizations with charts and graphs. I think a mindtool really has less to do with the tool itself and more to do with the crystallization of thinking.
Some other tools we've talked about, like flickr and delicious are really good researching tools. I have used flickr to get first person perspective on big events like Katrina and the Iranian election and subsequent protests. I have seen people use flickr's tagging capabilities, including museums and art history classes, to underscore important elements of a photo. In a photo taken during the Iranian election protests a photo taken of a woman in the protests tagged the cellphone that the woman was talking into, highlighting that the cell network had not yet been disabled at the time the photo was taken.
Besides the ability to do research by performing searches for pre-filtered results, the thing I find compelling about delicious is the folksonomy that you can see emerge. When I am researching a new area, it is helpful to me to see the tags that people have associated with the area. You can see the vocabulary that people use in association with the topic and how they've organized the hierarchy of information. That may not be an ideal means of knowledge creation, but I think it certainly is ideal in being able to quickly get an overall understanding of the landscape of a topic which enables you to conduct more pointed research.
I think what is most important about using these resources is the way they are used. I think it is most effective when these tools are used in the service of facilitating a larger initiative or project, not just tools for tools sake. When designing collaborative, knowledge constructing projects there are some things that I think are worth bearing in mind. The first is to consider what the tools afford. Some tools lend themselves to researching, others to collaboration and others as an information repository. Flickr and delicious are great for researching and sharing, but not for collaborating. In google docs and the now retired google wave, multiple people could be in the same document/environment working simultaneously and collaborating real time. Webspiration allows multiple users to work on the same piece of work, but only one at a time, which seems like asynchronous collaboration to me. One tool we haven't discussed is IM. I think there is potential for instant chat to be the thread of synchronous collaboration across even asynchronous tools.
Another consideration in using these tools has to do with account management. It becomes a bit overwhelming to have so many accounts with so many tools. I imagine that students over the course of time will have to manage not only a blog account, google account, flickr, delicious, wiki, and maybe even blackboard or ning accounts along with multiple email addresses - but also multiple accounts for most of those services for different grades, or even different subjects. We may end up needing another tool to keep track of all our accounts!
Some other tools we've talked about, like flickr and delicious are really good researching tools. I have used flickr to get first person perspective on big events like Katrina and the Iranian election and subsequent protests. I have seen people use flickr's tagging capabilities, including museums and art history classes, to underscore important elements of a photo. In a photo taken during the Iranian election protests a photo taken of a woman in the protests tagged the cellphone that the woman was talking into, highlighting that the cell network had not yet been disabled at the time the photo was taken.
Besides the ability to do research by performing searches for pre-filtered results, the thing I find compelling about delicious is the folksonomy that you can see emerge. When I am researching a new area, it is helpful to me to see the tags that people have associated with the area. You can see the vocabulary that people use in association with the topic and how they've organized the hierarchy of information. That may not be an ideal means of knowledge creation, but I think it certainly is ideal in being able to quickly get an overall understanding of the landscape of a topic which enables you to conduct more pointed research.
I think what is most important about using these resources is the way they are used. I think it is most effective when these tools are used in the service of facilitating a larger initiative or project, not just tools for tools sake. When designing collaborative, knowledge constructing projects there are some things that I think are worth bearing in mind. The first is to consider what the tools afford. Some tools lend themselves to researching, others to collaboration and others as an information repository. Flickr and delicious are great for researching and sharing, but not for collaborating. In google docs and the now retired google wave, multiple people could be in the same document/environment working simultaneously and collaborating real time. Webspiration allows multiple users to work on the same piece of work, but only one at a time, which seems like asynchronous collaboration to me. One tool we haven't discussed is IM. I think there is potential for instant chat to be the thread of synchronous collaboration across even asynchronous tools.
Another consideration in using these tools has to do with account management. It becomes a bit overwhelming to have so many accounts with so many tools. I imagine that students over the course of time will have to manage not only a blog account, google account, flickr, delicious, wiki, and maybe even blackboard or ning accounts along with multiple email addresses - but also multiple accounts for most of those services for different grades, or even different subjects. We may end up needing another tool to keep track of all our accounts!
Tuesday, April 13, 2010
Week 11 - Looking for weaknesses
Based on Professor Lowes' comments from last week, I tried to keep an eye for weaknesses in the research articles I read this week.
In the Haavind article, she looked at the relationship of low instructor contribution to high collaborative events amongst students. The study started with seven high collaboration classes, but only three classes fit the model of being low in instructor posting and high collaboration events which was sustained through the course, so only those classes were researched.
This is a small data set to start with, and then to throw out four classes and only look at the remaining three is really small. It also seems like there would be value in trying to understand where the contradictions came from. Class 7 had extremely high instructor contribution *and* sustained high collaboration. Why?
In the Zucker report, he looked at the impact of two approaches to promoting student-student interaction and collaboration. An experiment group was told to assign double point value towards grade based on student to student interaction, and was compared to a control group with the normal point assignment.
In this study, after four weeks into the fifteen week class, the teachers hadn't doubled the points for student to student interaction. At that point when they were asked to do so, they did, but, I think the pattern had already been established at that point and it ruins the study.
Zucker also administered a survey and reported a very high student response rate of 82%. It made me wonder how the survey was presented. Who did the students think the survey was coming from - the school, the teacher, a researcher? Just curious. Also, a survey pet peeve of mine is not having "other" as an option, or better yet and open text field. Without one of those options, and by making every question mandatory, he effectively forced the survey takers to agree with him, leaving no room for a response that he didn't consider.
I also noticed that the Rice article references a Cavanaugh study - I thought it was the one we read last week, but no. The one from last week covered distance ed from 1999-2004. The study Rice references covered distance ed from 1980-1998. Really?! Did they look at correspondence classes? Wow.
In the Haavind article, she looked at the relationship of low instructor contribution to high collaborative events amongst students. The study started with seven high collaboration classes, but only three classes fit the model of being low in instructor posting and high collaboration events which was sustained through the course, so only those classes were researched.
This is a small data set to start with, and then to throw out four classes and only look at the remaining three is really small. It also seems like there would be value in trying to understand where the contradictions came from. Class 7 had extremely high instructor contribution *and* sustained high collaboration. Why?
In the Zucker report, he looked at the impact of two approaches to promoting student-student interaction and collaboration. An experiment group was told to assign double point value towards grade based on student to student interaction, and was compared to a control group with the normal point assignment.
In this study, after four weeks into the fifteen week class, the teachers hadn't doubled the points for student to student interaction. At that point when they were asked to do so, they did, but, I think the pattern had already been established at that point and it ruins the study.
Zucker also administered a survey and reported a very high student response rate of 82%. It made me wonder how the survey was presented. Who did the students think the survey was coming from - the school, the teacher, a researcher? Just curious. Also, a survey pet peeve of mine is not having "other" as an option, or better yet and open text field. Without one of those options, and by making every question mandatory, he effectively forced the survey takers to agree with him, leaving no room for a response that he didn't consider.
I also noticed that the Rice article references a Cavanaugh study - I thought it was the one we read last week, but no. The one from last week covered distance ed from 1999-2004. The study Rice references covered distance ed from 1980-1998. Really?! Did they look at correspondence classes? Wow.
Tuesday, April 6, 2010
Define success
My job is to take web usage data for our site and help business owners understand if their section of the site is "successful" and how to make it better. I see some similar patterns in the meta analysis we read this week.
At the end of the day success looks different from situation to situation depending on your objective, and if a group or a company or an industry can't agree on the same metrics and what they mean, then no one really knows what is being reported.
So, in education, what is our objective? We want kids to learn. But how do you measure how well a kid has learned?
I propose that it will be very difficult, if not impossible, to move forward with meaningful, actionable research until we think about this question. What does learning look like? Is it the ability to recall facts, can it be demonstrated in the ability to write an essay? And, to Alejandro's point, what about cheating? Once we identify what success looks like, then students efforts turn to striving to mimic that standard, not learning.
What if we were to accept that in this day and age, anything can be searched for and found, so what is the benefit of memorization. My kids are being taught cursive, and for the life of me I cannot imagine why.
It seems to me like the challenge is to be able to take existing information, sort out the good from the bad, synthesize it, and figure out how to use it appropriately. What if learning was measured by what was created and the process of creating it?
We would look at a student or students ability to pick a project, search for the resources they need to understand it at an appropriate level and take that information and apply it. We'd evaluate their success in collecting and gathering the requisite depth and breadth of information; the level to which they've understood and used the information appropriately; and how well they took the information to create something of their own.
It is unrealistic to think that anyone can learn all that they need for the rest of their life from their time in school. The benefit to this approach is that students learn how to find their answers and be critical thinkers, so whatever the question that arises in the future, they'll know the process to take to build their understanding.
At the end of the day success looks different from situation to situation depending on your objective, and if a group or a company or an industry can't agree on the same metrics and what they mean, then no one really knows what is being reported.
So, in education, what is our objective? We want kids to learn. But how do you measure how well a kid has learned?
I propose that it will be very difficult, if not impossible, to move forward with meaningful, actionable research until we think about this question. What does learning look like? Is it the ability to recall facts, can it be demonstrated in the ability to write an essay? And, to Alejandro's point, what about cheating? Once we identify what success looks like, then students efforts turn to striving to mimic that standard, not learning.
What if we were to accept that in this day and age, anything can be searched for and found, so what is the benefit of memorization. My kids are being taught cursive, and for the life of me I cannot imagine why.
It seems to me like the challenge is to be able to take existing information, sort out the good from the bad, synthesize it, and figure out how to use it appropriately. What if learning was measured by what was created and the process of creating it?
We would look at a student or students ability to pick a project, search for the resources they need to understand it at an appropriate level and take that information and apply it. We'd evaluate their success in collecting and gathering the requisite depth and breadth of information; the level to which they've understood and used the information appropriately; and how well they took the information to create something of their own.
It is unrealistic to think that anyone can learn all that they need for the rest of their life from their time in school. The benefit to this approach is that students learn how to find their answers and be critical thinkers, so whatever the question that arises in the future, they'll know the process to take to build their understanding.
Wednesday, March 31, 2010
Collaboration, All Star style
Nardy and Sean have already done a good job of talking about the logistics of our project and our workings, so I'll just give you some personal observations about the experience.
I think the hardest part of the process was at the beginning when we were trying to settle on the platform we were going to use to collaborate. We all did a lot of double posting and emailing to make sure the message got through to each other. It was a bit time consuming with the over communication and checking into multiple platforms. I don't remember how it is we finally went with the wave, I guess it just naturally evolved that way.
I liked using the wave. In the past I don't think you were able to get email notifications when changes were made to the wave, but they apparently changed that feature and that made life a lot easier. After a while when the wave got so long that it became clunky, Nardy and I discovered that you could delete pieces. Once we were all on the same page, we did a bit of pruning and that made it more manageable.
Nardy and I also communicated with Google chat a lot, which I found to be a huge plus. Whether I was at work in front of my laptop, or around town with my mobile, I got pinged and we could collaborate on resources or answer each others questions.
I found doing the researching for the content and picking the tools to be the most fun. I found trying to put the framework up around it all to be the most daunting, but Sean had a clear vision and he pulled it all together.
I love the benefits that come from working in a team, seeing things in a new light and how collectively you can do something better than you could have individually. We had a really good team, and I'm so happy with how it all turned out!
I think the hardest part of the process was at the beginning when we were trying to settle on the platform we were going to use to collaborate. We all did a lot of double posting and emailing to make sure the message got through to each other. It was a bit time consuming with the over communication and checking into multiple platforms. I don't remember how it is we finally went with the wave, I guess it just naturally evolved that way.
I liked using the wave. In the past I don't think you were able to get email notifications when changes were made to the wave, but they apparently changed that feature and that made life a lot easier. After a while when the wave got so long that it became clunky, Nardy and I discovered that you could delete pieces. Once we were all on the same page, we did a bit of pruning and that made it more manageable.
Nardy and I also communicated with Google chat a lot, which I found to be a huge plus. Whether I was at work in front of my laptop, or around town with my mobile, I got pinged and we could collaborate on resources or answer each others questions.
I found doing the researching for the content and picking the tools to be the most fun. I found trying to put the framework up around it all to be the most daunting, but Sean had a clear vision and he pulled it all together.
I love the benefits that come from working in a team, seeing things in a new light and how collectively you can do something better than you could have individually. We had a really good team, and I'm so happy with how it all turned out!
Subscribe to:
Comments (Atom)
