Posts tagged ‘NCWIT’
It’s that time of year when Deans and Chairs start prodding students and teachers about course evaluations. What do the students think about their courses? What do the students think about their teachers?
There is a significant body of evidence that suggests that course evaluations are a stable measure about the teachers themselves. For example, the scores for a teacher are consistent across instantiations of the course over time (see Nira Hartiva’s work). However, they still might not be measuring something that we consider significant about teaching.
For example, it’s a mistake to think that student course evaluations tell us what a teacher knows about teaching. The teacher’s pedagogical content knowledge is invisible to the student. The student only sees what the teacher has decided to do to interact with the students. The student can’t see the knowledge that the teacher used in making that choice.
Three kinds of knowledge that are particularly relevant to a CS teacher are:
- Knowledge about how to teach. A good teacher knows more than one way to teach a particular subject, and knows to change methods for a given student or to change the pace of a class. When I see students driving away in the back of my class, I know that it’s time for a Peer Instruction activity.
- Knowledge about misconceptions. As was shown in Phil Sadler’s exceptional study (see blog post), a characteristic of teacher expertise is knowledge about what students typically get wrong. Based on that knowledge, teachers can address those misconceptions, and lead students to discover and correct the misconceptions themselves.
- Knowledge about how to broaden participation in computing, which is particularly relevant to CS teachers. These include how to teach avoiding stereotype threat and triggering the imposter phenomenon, about how to give everyone a voice in the class and not let the loud and boisterous define the teacher’s perceptions of the course. I can offer a negative example, taken from real life but might have been invented after reading the negative examples in Unlocking the Clubhouse.
Teacher: How many of you students had Python in a previous class?
(Most students raise their hands, since it’s the language used in the pre-requisite class.)
Teacher: Well, you learned a terrible language. You’ll have to forget everything you know if you want to pass this class.
(Every student suffering imposter syndrome at this point decides to drop.)
This teacher actually has quite high course evaluation scores — and double the drop rate of every other teacher of that class.
Pedagogical content knowledge (PCK) is the key difference between novice and expert teachers, but is invisible to students. This is another reason why student evaluations of teaching (aka, Student Reviews of Instruction (SRI)) are inadequate as measures of teaching quality. They can’t measure a key indicator of teacher expertise.
I’ve been wondering how post-secondary teaching might change if we were to take a PCK perspective seriously. The knowledge of good teaching is definable and measurable.
- We might define courses not just in terms of learning objectives but in terms of what knowledge the teacher should have to teach the class effectively.
- We could evaluate University and College teachers based on their PCK — literally, taking a test on what they know about teaching the class.
- PCK tests would finally create an impetus for University and College faculty to pursue professional development — that’s where they’d learn the teaching methods, student misconceptions, and methods for encouraging BPC that they need to answer the PCK tests. One might even imagine teachers taking a class on how to teach a new class that they’ll be offering in the future — preparing for a course by developing expertise in teaching that course. What an interesting thought that is, that higher education faculty might study how to teach.
BBC is giving away 1 million mini computers so kids can learn to code: Prediction — little impact on broadening participation
I agree that these boards are cool, but I’m a geeky white guy. I predict that they’ll have little impact in increasing access to computing education or in diversifying computing. Bare board computers are not more attractive to teachers, so we don’t get more teachers going into CS. They’re not more attractive than existing computers to women who aren’t already interested in computing. Why are people so excited about handing out bare board computers to grade school children? Is this just white males emphasizing the attributes that attract them? Judith Bishop of MSR (whose TouchDevelop will work on these new computers) says that she’s seen girls get engaged by these new computers, but nobody has done any research to see if that’s more than the 20% of females who get interested in computing now, or if that happens outside of the pilot classrooms.
Currently in development, the Micro Bit is a small piece of programmable, wearable hardware that helps kids learn basic coding and programming. It could act as a springboard for more advanced coding on products, such as the single-board computer Raspberry Pi, according to the BBC.
Children will be able to plug the device into a computer, and start creating with it immediately.
“BBC Make it Digital could help digital creativity become as familiar and fundamental as writing, and I’m truly excited by what Britain, and future great Britons, can achieve,” BBC director general Tony Hall said in a statement Thursday.
Nice blog post from Barbara Ericson exploring the lack of women in the new surge in CS undergraduate enrollment.
A Surge in Majors, but Where Are the Women?
While a number of colleges and universities in the United States have recently seen a tremendous increase in the number of students who want to major in computing, the percentage of women who are interested is still low. A study conducted by the Association for Computing Machinery and the WGBH Educational Foundation in 2008 found that only 9 percent of college-bound teen girls thought that a career in computing was a very good choice for them, and only 17 percent thought that it was a good career choice. Teen girls associated computing with typing, math, and boredom. While the percentage of bachelor’s degrees awarded to women in the United States did increase from 11.7 percent in 2010–11 to 12.9 percent in 2011–12, women are still dramatically underrepresented.
The Percentage of Women Taking the Computer Science AP Exam Lags
The Advanced Placement (AP) computer science A course is equivalent to a college-level introductory computer science course. It focuses on object-oriented programming in Java. In 2014, only about 20 percent of AP computer science A exam takers were women. While that was an increase from the previous year, when the percentage was 18.5 percent, it is still far below the percentage of women who took the AP calculus AB exam (48.7 percent) and the percentage of women who took the AP biology exam (59 percent). It is even well below the percentage of women who took the physics B exam (34.7 percent), as shown below.
Nice story and presentation from Katie Cunningham about how she informed her faculty about why there are so few women in CS, and what they can do about it.
I based the main arc of my presentation on a book chapter by Whitecraft and Williams that Greg Wilson of Software Carpentry was kind enough to forward to me. It’s an evenhanded look at much of the research in this area, including theories that are often out of favor in most places I frequent. It served as a great overview, though I felt it could have focused more on issues involving differences in prior programming experience pre-college and intimidation brought on by “nerdy strutting“. (Update: I just discovered a fantastic 2012 report by NCWIT that can also serve as a great overview. It covers cultural issues more comprehensively, with more recent research and more focus on the pre-college years.)
C is Manly, Python is for “n00bs”: Our perception of programming languages is influenced by our gender expectations
Surprising and interesting empirical evidence that language use is mostly gender-neutral. Our expectations about gender influence how we think about programming languages. These perceptions help explain the prevalence of C and C++ in many undergraduate computing programs.
There is also a gendered perception of language hierarchy with the most “manly” at the top. One Slashdot commenter writes, “Bah, Python is for girls anyways. Everybody knows that PERL is the language of true men.” Someone else responds, “Actually, C is the language of true men…” Such views suggest that women might disproportionately use certain languages, but Ari and Leo found in their programmer surveys that knowledge of programming languages is largely equivalent between genders. Women are slightly more likely to know Excel and men are slightly more likely to know C, C#, and Ruby, but not enough to establish any gendered hierarchy.
I mentioned (in a previous blog post) Google’s awards program to fund innovative efforts that deal with rising enrollments in CS while improving diversity. They’ve just announced the six awardees: CMU, Duke, Mount Holyoke, George Mason, Rutgers, and Berkeley. The plans include mentor training, teaching fellows, new kinds of class structures (e.g., optional mini-lectures, small group sessions, self-paced elements, and periodic skills demos based on martial arts), new technology tools, and collaboration spaces.
More details are in the Google blog post below.
One of Google’s goals is to surface successful strategies that support the expansion of high-quality Computer Science (CS) programs at the undergraduate level. Innovations in teaching and technologies, while additionally ensuring better engagement of women and underrepresented minority students, is necessary in creating inclusive, sustainable, and scalable educational programs.
To address issues arising from the dramatic increase in undergraduate CS enrollments, we recently launched the Computer Science Capacity Awards program. For this three-year program, select educational institutions were invited to contribute proposals for innovative, inclusive, and sustainable approaches to address current scaling issues in university CS educational programs.
The Always Super Bowl commercial “Like a Girl” was compelling (see video here). When did “Like a Girl” become an insult?
The blog post linked below (thanks to Kate Harlan for this) offers several stories of female programmers presumed to be less-of-a-programmer because they’re females. These are sad stories.
People are generally willing to believe that I can program, since I’m a white, male CS professor who has written programs in the past (e.g.,the original Swiki and Emile). In my family, we all know that Mom is the expert programmer. All three of our kids took AP CS, and they all asked Barb for help, with me only as a last resort. When we were writing our books, I’d leave notes next to my searching or sorting examples in the LaTeX source for Barb, my co-author: “Yeah, I know that this isn’t quite right. Can you fix it please?” I wrote the first version of the Java class files for Media Computation and JES. Then Barb looked at them, tsk-tsk-ed a bit, and made them work well and made them readable. My wife is an amazing programmer, far better than me #LikeAGirl.
I’m sure that Barbara has had people question her as a programmer, and more than they typically question my abilities as a programmer — while the real ability is the opposite.
One category of reactions that I receive all the time as a programmer that presents as feminine is: No one believes I am a programmer.
I can’t tell you how many people, when meeting me and hearing my profession, tell me that I look like a designer, someone in accounting, someone in marketing, anything but a programmer.
I have been a TA for weekend workshops that teach women to code. My male co-TA’s constantly asked me throughout the workshop how I was enjoying learning to program.
Apparently, presenting as feminine makes you look like a beginner. It is very frustrating that I will either look like not a programmer or look like a permanent beginner because I have programmed since age 8. I have basically always wanted to be a programmer. I received undergrad and grad degrees from MIT. I’ve worked as a visiting researcher in Honda’s humanoid robotics division on machine learning algorithms for ASIMO.
I don’t think that any of these things make me a better programmer; I list them because I am pretty sure that if I were a white man with these credentials or even less than these credentials no one would doubt my programmer status.