As chair, I spend quite a bit of time with numbers of various sorts. There are budget numbers and enrollment numbers. There’s the number of sections of courses per term and per year. Relatedly, there are FTE numbers, or how many warm bodies do we have to teach courses and how many courses are they teaching at any given time….you get the idea.
At this time of year, when sophomores declare their majors, I hyper-focus on numbers related to the sophomores. This includes the number of students who’ve declared as computer science majors, the difference between the size of this year’s class and the previous few years’ classes, the percentage of women and underrepresented minorities, and the “yield” from certain courses, among others. Looking at these numbers gives me the opportunity to assess the state of the department on a mini-scale: a quick way to determine if we’re where we want to be and heading in the right direction.
In many respects, our numbers are excellent. My quick and possibly inaccurate sampling of the usual suspects indicates that we are now the largest department on campus in terms of majors in the sophomore, junior, and senior classes (tied with Biology), and that we have the largest number of majors in the sophomore class (followed by Biology and Economics, who if memory serves are tied). At the time of this writing, we have 50 majors, which is right in line with the past 2 classes (55 in the current junior class and 54 in the current senior class). I suspect we will stabilize in the mid-50s once the double majors declare—there are some omissions from our current list that I’ve already talked with about double-majoring, so I am just waiting for them to come to me with forms in hand at some point over the next few weeks.
There is one number of which I am insanely proud: I taught a first-year seminar in the fall of 2013 on Human-Centered Computing, and 7 of the 16 students in that course (who are now sophomores) declared as computer science majors. I was hoping for a good yield from that course, but frankly I was stunned at just how high the yield was! What an argument for the importance of teaching courses outside the major sequence. (Note to self: remember this when putting together the 2016-17 schedule!)
There are some numbers that concern me. Our major population is diversifying, but we could definitely be doing much better in this regard. Also troubling: after 2 years of 30-35% women majors, our sophomore class is just 20% women. Again, these numbers might creep up a bit once the double majors declare, but the percentage is not going to change significantly.
The decrease in the percentage of women has me pondering the possible reasons. Has there been a culture shift in the department? Are we doing something differently in Intro or in our “first-tier” required courses (data structures, math of CS, organization and architecture) that we weren’t doing 3-4 years ago? Are the larger class sizes off-putting more to women than to men? Are there things that we’re neglecting to do, now that we’re swamped with students, that we used to do, to foster community? (For instance, I used to send short, personal emails to Intro and Data Structures students encouraging them to take more CS courses, but I don’t always remember to do that to the same degree as I did in the past. What effects does this have on retention in the major?) In short, what’s changed?
Another factor I pondered on my walk across campus to class today: what effect does having senior faculty teach some of those “key” courses have on recruitment and retention? Now, we have a vibrant cohort of assistant professors and visitors who are doing a fabulous job, and many of them are teaching those key courses. But I think it’s important, for many reasons, to have
us old fogies the senior, tenured folks at these entry points, too. And that’s the problem: we are so busy and so over-committed as a senior group that we’re teaching many fewer courses. For instance: There are 4 tenured professors in my department (2 full, 2 associate). The normal teaching load per tenure-track professor is 5 courses a year (2-2-1 or some variation). So among us, we should be teaching 20 courses. Next year? We are teaching 11. One person is on sabbatical all year, one is essentially teaching half-time because he was elected faculty president, and two of us have a course release (me for being chair, another colleague for chairing a large campus committee). And two of us are leading senior capstone groups as one of our “courses”, which means that we’re teaching 2 fewer “classic” courses. And because of scheduling and expertise constraints, with maybe 1-2 exceptions we’re teaching all upper-level courses.
So what are my take-away points, after this
navel-gazing romp through the numbers?
- We have a vibrant department. Our enrollments are healthy and strong, and this is translating into majors. And our majors are awesome—I’m very excited about our newest class!
- We need to continue to prioritize “outreach” in terms of first-year seminars and similar courses. It’s definitely worth it, even it if means offering one fewer course for our majors per year.
- We need to take a closer look at our culture. I’d like to informally talk to students to get a sense of what’s happening “on the ground”. In particular, I want to chat with the leaders of our 2 student groups, particularly our Women in Computing group, and our SDAs (student departmental advisors) and get their thoughts on what we’re doing well and what we might do differently.
- Similarly, we need to individually look at what we’re doing as faculty to encourage our students to explore computer science, and make sure all those best practices we’ve honed over the years are still in play.
- Frankly, I’m not sure what to do about the overcommitted senior faculty issue. I sense this issue is not going to go away anytime soon—to be honest, I’d be shocked if one of us old fogies is not tapped for an administrative post in the next 3-5 years. But are there ways we can work with the faculty affairs committee, for instance, to ensure that we can both serve the college *and* staff our courses appropriately? (For instance, could this committee check with departments before allowing a nomination for a major campus position to move forward, to make sure they are not inadvertently causing a staffing crisis for that department? In short, could opportunities be timed better for *all* parties involved?)
The CS department is a totally different place now than when I first arrived. We worked hard as faculty to grow what we hope is a welcoming, open, fun culture. I am confident that we can continue this moving forward, but just as it took lots of energy and commitment to get us here, so too will it take energy and commitment to keep us here. I hope we’re up to the task.