Skip to main content

Abolish universities? Not so fast

The NY Times is carrying an editorial today from Mark C. Taylor, the chair of the Religion department at Columbia, saying that we need to rethink the structure of graduate education, and universities as a whole, to make them more relevant in today's world. The article is generally thought-provoking, but dead wrong when it comes to science and engineering. Unfortunately, the article does not qualify its statements as being relevant only to the humanities and social sciences, which is too bad considering that some readers might extend this flawed line of thinking to apply to other fields.

I'm surprised the author would be so careless to say things like:
"Most graduate programs in American universities produce a product for which there is no market..."
"Young people enroll in graduate programs ... all because of the illusory promise of faculty appointments." [Emphasis mine.]
What planet is this guy from? What he really means is that in the areas of "religion, politics, history, economics, anthropology, sociology, literature, art, religion and philosophy" (the author's all-encompassing list of the realms of human thought that apparently really matter) it is damned hard to get a decent job after graduate school, and I agree. But this has little to do with the situation in the sciences and engineering, where graduate students go on to a wide range of careers in industry, government, military, and, yes, academia.

I grant that it is possible that we are headed towards a brick wall in these other fields. According to the latest Taulbee survey, Ph.D. production in Computer Science has been skyrocketing, at its highest levels since the survey was started. However, far more students are going into industry than academia. Even for students dead set on a faculty position, many can get a job straight out of graduate school -- postdocs are still the exception rather than the rule. This situation could change, but I'm not sure it's time to end universities as we know them. Religion departments are maybe another matter.


  1. I'd disagree with you here about the prospects for a CS grad student in academia. Luis van Ahn had a great post on his blog about the irrationality of choosing to go to graduate school in CS if your goal is to be a faculty member in a top or mid-level department ( In order to get into a top graduate schoo (which is required to get a job at any top 50 programl, you need to have done very well as an undergrad. If you're good and lucky enough to finish your PhD, the numbers are not in your favor on the job market and I think that's been making postdocs far more common. I've definitely noticed an uptick in the number of postdocs we interview for junior faculty positions.

    Compare that to what would happen if this same top student went into industry straight out of undergrad rather than going to graduate school. They'd likely be making a lot more money, deal with less stress, and wouldn't have had all of the uncertainty and pain of graduate school.

    I think being a professor is a great job, but I do think too many students in CS do enroll in graduate school with the illusory promise of faculty appointments and most graduate programs in CS do produce students who have no chance of being hired at the school where they get their PhD.

    Great blog, by the way.

  2. Good point. The thing is, I'm not worried about those "stressed" grad students in CS. If they aren't doing well, and not on track to get the kind of job they want, they should just drop out of grad school and go get that industry job. This is likely not true for the poor religion and history grad students!


Post a Comment

Popular posts from this blog

Why I'm leaving Harvard

The word is out that I have decided to resign my tenured faculty job at Harvard to remain at Google. Obviously this will be a big change in my career, and one that I have spent a tremendous amount of time mulling over the last few months.

Rather than let rumors spread about the reasons for my move, I think I should be pretty direct in explaining my thinking here.

I should say first of all that I'm not leaving because of any problems with Harvard. On the contrary, I love Harvard, and will miss it a lot. The computer science faculty are absolutely top-notch, and the students are the best a professor could ever hope to work with. It is a fantastic environment, very supportive, and full of great people. They were crazy enough to give me tenure, and I feel no small pang of guilt for leaving now. I joined Harvard because it offered the opportunity to make a big impact on a great department at an important school, and I have no regrets about my decision to go there eight years ago. But m…

Rewriting a large production system in Go

My team at Google is wrapping up an effort to rewrite a large production system (almost) entirely in Go. I say "almost" because one component of the system -- a library for transcoding between image formats -- works perfectly well in C++, so we decided to leave it as-is. But the rest of the system is 100% Go, not just wrappers to existing modules in C++ or another language. It's been a fun experience and I thought I'd share some lessons learned.

Why rewrite?

The first question we must answer is why we considered a rewrite in the first place. When we started this project, we adopted an existing C++ based system, which had been developed over the course of a couple of years by two of our sister teams at Google. It's a good system and does its job remarkably well. However, it has been used in several different projects with vastly different goals, leading to a nontrivial accretion of cruft. Over time, it became apparent that for us to continue to innovate rapidly wo…

Running a software team at Google

I'm often asked what my job is like at Google since I left academia. I guess going from tenured professor to software engineer sounds like a big step down. Job titles aside, I'm much happier and more productive in my new role than I was in the 8 years at Harvard, though there are actually a lot of similarities between being a professor and running a software team.

I lead a team at Google's Seattle office which is responsible for a range of projects in the mobile web performance area (for more background on my team's work see my earlier blog post on the topic). One of our projects is the recently-announced data compression proxy support in Chrome Mobile. We also work on the PageSpeed suite of technologies, specifically focusing on mobile web optimization, as well as a bunch of other cool stuff that I can't talk about just yet.

My official job title is just "software engineer," which is the most common (and coveted) role at Google. (I say "coveted&quo…