What can I do today to create a more inclusive community in CS? Guest Post from Cynthia Lee

September 28, 2015 at 8:50 am 5 comments

In July, Cynthia Lee, Leo Porter, Beth Simon, and I held a workshop (funded by the NSF IUSE program) for new faculty at research-intensive universities, to help them to be more effective and efficient teachers. We had eight new faculty attend. We taught them about peer instruction, worked examples, how to create a syllabus, techniques for dealing with plagiarism, how to make time for teaching, and how to create a more inclusive classroom. The response was terrific. As one participant told us, “I can’t believe how much actionable knowledge I picked up about teaching in just a day and a half!”

We’ll be inviting new faculty from research-intensive universities again in Summer 2016.

The below list was created by Cynthia Lee for the workshop participants. I loved it and asked if I could offer it here as a guest post. I’m grateful that she agreed.


 

  • Email top performers on a recent homework or exam to congratulate them; be sure to include a diverse group.
  • Personally invite a woman or minority student who is doing well to major in CS, apply to an internship, or go to grad school. If your TAs work with small groups of students in a discussion section, have them do this as well.1
  • Review today’s lecture slides to make sure that your gender pronouns are varied, and not in ways that conform to stereotype.
  • Avoid heteronormative examples (e.g., bijective function between sets “boys” and “girls”).
  • When using arbitrary names in examples, choose a broader selection (Juan, Neha, Maria, Mohammed, instead of just Jane Doe and John Smith). To represent your school’s population, use a previous quarter roster for ideas.
  • At the beginning of the quarter, ask each student to email you to introduce themselves by naming one of their core values, and one way that CS relates to or could be used in service of that core value (or write it down in class, and/or share with a neighbor in class).2
  • Never say, “This UI is so easy your mom could use it” or “How would you explain this to your mom?” or other phrases that equate women with lack of tech savvy. 3
  • Review today’s lecture slides to make sure that stock photos and illustrations with people in them include diverse races and genders in non-stereotyped roles.
  • Believe that hard work and effective practice matters more than DNA. Your beliefs influence students’ beliefs and impact their performance. 4
  • Take a moment in class today to encourage students to focus on their “slope,” not their “y-intercept.” That is, in the long run it matters how fast you’re growing and learning, not advantages or deficiencies in where you started. 5
  • Start class today by telling the students you’re proud of them and how hard they are working. Tell them you are enjoying working with them this quarter.
  • Start class today by renewing your encouragement to students to come to office hours. Explicitly instruct them how to do it: “you don’t need to have a particular question-you’re welcome to just stop by for 5 minutes to introduce yourself” and “I’m not just here for homework questions-if you are considering changing your major to CS and want to talk about it, if you want to know what it’s like to work as a software engineer, if you are thinking about applying to grad school but don’t know where to begin, I’m happy to discuss that kind of thing as well.”
  • Have very clear written expectations for student work (coding style, project components, etc.). Where possible, show sample solutions exactly as you would want a student to write them (don’t just give a “sketch” of the solution).
  • Allow and encourage pair programming on assignments. 6
  • Provide students with clear and timely feedback, including class-wide distribution data. Women and minority students often fear the worst about their position relative to the class and can be reassured by data. 7
  • After a midterm exam, step through the math showing that they can still pass the course even if they did poorly. It’s just some multiplication, but take the time to talk about it. Be factual-no need to “sugar coat”-but provide facts that will help students who think things are worse than they really are.
  • When a student is speaking, wait for the student to finish then count “one one-thousand, two one-thousand” in your mind before responding. Both men and women are prone to prematurely cutting off women when they speak. You may do this unconsciously unless you consciously add that pause. 8
  • Occasionally choose a lecture to actually write a tally of how many times you’ve called on men vs women in the class. Both men and women are prone to calling on men more often. You may do this unconsciously unless you consciously do otherwise. 9
  • Actively mitigate when students may be intimidating each other. When a student uses jargon in a question (often one of those questions that is more of a boast than a real question), explicitly identify when you expect that most students will not be familiar with that jargon, and/or it is not something other students are expected to know for the class (“Thanks for your comment. For the rest of the class, I’m sure most of you aren’t familiar with some of those terms-don’t worry, you’re not alone. Those terms are outside the scope of this class and not necessary to know.”)
  • Ensure that you and your TAs call each student by their preferred name and gender pronoun-including allowing students to write their preferred name on homework and exams-even if these do not match their current legal and/or registrar records of name and sex. This issue deeply affects transgender students, and also many students who prefer to have an alternate anglicized name. Some institutions are good about allowing students to easily make these changes with the registrar so the preference will automatically show up on your roster. Find out about your school’s policies. You could also put a statement in your syllabus that you welcome students to email you about their preference.
  • Watch out for examples or anecdotes about your childhood or daily life that may cause students to feel excluded for economic reasons (e.g., talking about pricey gadgets or vacations in Hawaii as normal). Even if you know that you did not experience these things and are simply using them as an example, students don’t know that and can mistakenly assume you are referring to them in a normative way.
  • Mid-quarter, reach out to a student who has filed a disability accommodation form with you and ask them if their needs are being met in your class. Reaffirm your commitment to complying with their approved accommodations and your willingness to receive complaints if there is a problem.
  • Encourage your colleagues to do the items on this list. Advertise your good example by bringing up your performance of these items in conversations with other faculty.

Footnotes:

  1. Holly Lord and Joanne McGrath Cohoon. “Recruiting and Retaining Women Graduate Students in Computer Science and Engineering,” 2006. ↩︎
  2. Research shows this intervention mitigates stereotype threat. Reduced racial gap by 30%. https://www.gsb.stanford.edu/insights/value-values-affirmation. ↩︎
  3. This sexist trope is something women have been working to expunge from our vocabulary. Unfortunately, still often seen in discussion of UI design. http://geekfeminism.wikia.com/wiki/So_simple,_your_mother_could_do_it ↩︎
  4. Carol Dweck. “The New Psychology of Success.” http://s3.amazonaws.com/ebsp/pdf/mindsett.pdf This research shows that minority students perform worse in classes where the professor believes in a “fixed mindset” (talent is innate) when compared to performance in classes where professor has a “growth mindset” (talent can be developed through effort). See also CS-specific work on mindsets: Laurie Murphy and Lynda Thomas. “Dangers of a fixed mindset: implications of self-theories research for computer science education.” ITiCSE 2008. ↩︎
  5. Articulating this idea as slope/y-intercept is from Professor John Ousterhout of Stanford. ↩︎
  6. Among other research showing benefits of pair programming: Leo Porter and Beth Simon. “Retaining nearly one-third more majors with a trio of instructional best practices in CS1,” SIGCSE ’13. http://dl.acm.org/citation.cfm?id=2445248 ↩︎
  7. These fears are related to “Imposter Syndrome”-even highly talented students from under-represented groups fear that they are unskilled, and more unskilled than everyone else. Overview of Imposter Syndrome research: https://en.wikipedia.org/wiki/Impostor_syndrome ↩︎
  8. Occasioned by a news item about a panel discussion in Silicon Valley, NYTimes reviews research on women being interrupted when speaking: http://nytlive.nytimes.com/womenintheworld/2015/03/19/google-chief-blasted-for-repeatedly-interrupting-female-government-official/ ↩︎
  9. Jere Brophy and Thomas Good. “Teachers’ communication of differential expectations for children’s classroom performance,” 1970. http://psycnet.apa.org/journals/edu/61/5/365.pdf ↩︎

Entry filed under: Uncategorized. Tags: , , .

Student and Teacher CSP Ebooks are now Available Steve Cooper heads to University of Nebraska-Lincoln

5 Comments Add your own

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


Recent Posts

September 2015
M T W T F S S
« Aug   Oct »
 123456
78910111213
14151617181920
21222324252627
282930  

Feeds

Blog Stats

  • 1,294,209 hits

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 4,598 other followers

CS Teaching Tips


%d bloggers like this: