Posts tagged ‘computing education’
This is a really cool announcement. I believe that computing helps with all kinds of STEM learning, and admire the work at Northwestern on Agent Based Learning in STEM, Project GUTS, and Bootstrap. It’s particularly important for getting CS into schools, since so few schools will have dedicated CS teachers for many years yet (as described here for Georgia). I’m excited to see that Bootstrap will be moving into Physics as well as Algebra.
Bootstrap, one of the nation’s leading computer science literacy programs, co-directed by Brown CS faculty members Shriram Krishnamurthi and Kathi Fisler (adjunct), continues to extend its reach. Bootstrap has just announced a partnership to use its approach to building systems to teach modeling in physics, an important component of the Next Generation Science Standards (NGSS). This project is a collaboration with STEMTeachersNYC, the American Association of Physics Teachers, and the American Modeling Teachers Association.
These are the right sort of questions to be asking, and then using when creating real programs. How would we get more undergraduate computing majors to consider teaching? We can’t do much about salary. Free tuition and student loan forgiveness are feasible and could result in many more teachers (and are being explored by ECEP states).
CERP asked undergraduate computing majors what would increase their interest in becoming a middle or high school computing teacher. As seen in the above graphic, financial incentive in the form of a higher teaching salary, free tuition for teacher training, and forgiven student loans were the top factors increasing students’ interest in becoming a middle or high school computing teacher. These findings provide insights into how to generate more computing educators for the K-12 school system, which is becoming increasingly important, given recent efforts to promote widespread K-12 computing education.
I was surprised to see the numbers quoted below. PhD unemployment is that high? Aman Yadav just pointed me to an article in The Atlantic, with even more depressing news about the number of years to PhD, the debt after PhD, and the percentage of unemployment — see here.
CS is grouped into Engineering, so I tried to find the stats just on CS PhD’s. The 2014 Taulbee survey (see link here) says “The unemployment rate for new Ph.D.s again this year was below one percent.” But goes on to say, “The fraction of new Ph.D.s whose employment status was unknown was 19.7 percent in 2013-14; in 2012-13 it was 20.8 percent. It is possible that the lack of information about the employment of more than one in six graduates skews the real overall percentages for certain employment categories.” It’s not clear that we know what happens to new CS PhD’s, and what the real unemployment rate is.
Percent of Doctorate Recipients With Job or Postdoc Commitments, by Field of Study
Field 2004 2009 2014
All 70.0% 69.5% 61.4%
Life sciences 71.2% 66.8% 57.9%
Physical sciences 71.5% 72.1% 63.8%
Social sciences 71.3% 72.9% 68.8%
Engineering 63.6% 66.8% 57.0
Education 74.6% 71.6% 64.6%
Humanities 63.4% 63.3% 54.3%
I’ve raised the concern before that the CS for All effort might mean “CS for only the rich” (see post here). Our data from Georgia suggest that few students are actually getting access to CS education, even if there is a CS teacher in the school (see post here). Kathi Fisler, Shriram Krishnamurthi, and Emmanuel Schanzer offer a Blog@CACM post where they consider how we make sure that #CS4All is equitable.
Mandating every child take a computing class is a great way to ensure everyone takes CS, but very few states, cities, or even school districts are in a position to hire enough dedicated CS teachers or offer dedicated CS classes to reach every child. Recent declarations from several major districts that “every child will learn to code” often place impossible burdens on schools. Similarly, few schools can afford to offer CS programs that require cutting-edge computers, expensive consumables, or technology that requires significant maintenance.
To truly achieve CS4All Students in a sustainable way, equity and scale are issues that must be built in by design. Similarly, initiatives have to think about differently-abled users from scratch, not just bolt them on as an afterthought. Accessibility needs to be designed into software, curriculum, and pedagogy from the earliest stages.
The “move fast and break things” culture of computing is no help here. Right now, computing education has enormous attention. That day will pass. By the time we get around to focusing on equity, we may have depleted the energy left to overhaul computing curricula. Instead, we have to think this through at the very outset. Another computing principle is that products typically get one shot at gaining users’ attention. For the foreseeable future, this is that one shot for computing education.
Top business leaders, 27 governors, urge Congress to boost computer science education – The Washington Post
I saw on Facebook that Hadi Partovi was at Congress. Now I see why — there’s an effort underway to get Congress to fund more in CS education. I’m wondering what they want to get funded. Incentives for teachers? Professional development? Pre-service education? Does someone know the details?
Despite this groundswell, three-quarters of U.S. schools do not offer meaningful computer science courses. At a time when every industry in every state is impacted by advances in computer technology, our schools should give all students the opportunity to understand how this technology works, to learn how to be creators, coders, and makers — not just consumers. Instead, what is increasingly a basic skill is only available to the lucky few, leaving most students behind, particularly students of color and girls.
How is this acceptable? America leads the world in technology. We invented the personal computer, the Internet, e-commerce, social networking, and the smartphone. This is our chance to position the next generation to participate in the new American Dream.
Survey for CS Faculty on use of Evidence-based Instructional Practices: Guest blog post from Scott Grissom
Clearly an important topic — I’m sharing this here, with thanks to Scott.
The SIGCSE Committee on Evidence-based Instructional Practices is investigating the most commonly used teaching practices in CS education (such as classroom activities, student learning goals and assessment techniques). We are replicating a study from physics education that surveyed over 800 faculty. We have already used the validated instrument in a pilot study with twelve institutions and have received 160 responses so far.
Rather than simply send a survey link to this mailing list that might create a skewed sample, we are inviting entire CS departments to survey their members. Our goal is to survey instructors from many 2-year, 4-year, private, public, research and teaching institutions.
The project will allow us to accomplish three important objectives:
- Provide a baseline of instructional practices used in CS higher education.
- Compare CS instructional practices with other STEM disciplines.
- Inform efforts to reform CS education by increasing the adoption of evidence-based instructional practices.
WILL YOU INTRODUCE US TO YOUR COLLEAGUES?
Best survey practices have shown that an introduction from a trusted colleague increases response rates. This is where you can help! Are you willing to support the CS education community by introducing us to your colleagues and encouraging them to complete the survey?
Please contact Scott Grissom BY FRIDAY APRIL 15 if you are willing to help, and we will provide more information about what we will ask you to do.
SIGCSE Committee on Evidence-based Instructional Practices
– Scott Grissom, Grand Valley State University, email@example.com
– Sue Fitzgerald, Metropolitan State University, firstname.lastname@example.org
– Renée McCauley, College of Charleston, email@example.com
– Laurie Murphy, Pacific Lutheran University, firstname.lastname@example.org
Brian Drayton has now written a couple of posts critical of the CS for All initiative (one is linked below, and here’s another one), and his points are well taken. In my book on Learner-Centered Design of Computing Education, I consider several possible reasons for teaching CS to everyone. I prefer the same ones that he does, and I agree that much of the initiative is poorly justified. I do not believe that we should put CS into all schools in order to make high school graduates “job-ready” (see the White House release using that phrase).
I agree that “everyone should code” is both unrealistic and poorly justified, as it has currently been advocated. I think we could make more progress (both in expanding people’s understanding of computer science or computation, and in empowering people to adopt such knowledge as a valuable tool for growth, creativity, and employment) if we did a better job envisioning what we’d like a classroom to look like that is deeply conversant with the tools and the insights of computer science in the same way that the classroom is already deeply infused with the tools and insights of literacy and numeracy.