Is research sick?

One of the most important database researchers of all time, Michael Stonebraker, has given a talk recently on the state of database research. I believe that many of his points are of general interest:

  • We have a lost our consumers… Researchers write for other researchers. They are being insular and ultimately irrelevant.
  • We ignore the important problems… Researchers prefer to focus on the easy problems they know how to solve right away.
  • Irrelevant theory comes to dominate… Making things work in the real work is harder than publishing yet-another-theory paper.
  • We do not have research taste… Researchers jump on whatever is fashionable with little regard to whether it makes sense (XML, Semantic Web, MapReduce, Object databases and so forth).

The core message that Stonebraker is trying to pass is that the seminal work he did years ago would no longer be possible today.

I do not share his views, but I think that they are worth discussing.

The fact that we are publishing many papers is not, by itself, a problem. The irrelevant theory can be ignored. The fact that many people follow trends mindlessly whereas only a few make their own ways, is just human nature.

So what is the real problem?

My take is that there is an underlying supply-and-demand issue. We are training many more PhDs than there are desirable tenure-track jobs. This puts early-career researchers in a overcompetitive game. If you can signal your value by getting papers accepted at competitive venues, then that is what you are going to do. If you need to temporarily exagerate your accomplishments, or find shortcuts, maybe you will do so to secure the much needed job.

You cannot magically make a field less competitive without tackling the supply and demand. Either you reduce the number of PhDs, or you increase the number of desirable research jobs. I’d vote for the latter. Stonebraker says nothing about this. In fact, though I like him well enough, he is an elitist who cares for little but the top-20 schools in the US. The problem is that even just these top-20 schools produce many more PhDs than they consume. Is it any wonder if all these PhD students desperately play games?

The reason Stonebraker was able to get a tenure-track job in a good school when he completed his PhD without any publication is… Economics 101… there was no shortage of tenure-track jobs back then.

Is it any wonder if the new professors recruited in an overcompetitive system are status-obsessed folks?

There is no doubt that some PhD students and young faculty members will pursue volume at the expense of quality and relevance. However, there is no reason to believe that the best American universities (the ones Stonebraker cares about) do not already take this into account. Do you really think you can go from a PhD program to a faculty job at Harvard, Stanford or MIT without one or two great papers? Do you really think that these schools will pass on someone who has produced seminal work, and pick the fellow who has a large volume of irrelevant papers instead? If that’s the case, where are the examples?

Meanwhile, there are more great papers being published in my area, in any given year, than I can read. Here is a hint: you can find many of them on arXiv. No need to go to an expensive conference at some remote location. It might be the case that some disciplines are corrupted, but computer science research feels quite worthwhile, despite all its flaws.

Published by

Daniel Lemire

A computer science professor at the Université du Québec (TELUQ).

4 thoughts on “Is research sick?”

  1. It looks like your underlying assumption is that a PHD is only good for doing basic research or teaching.
    If so, yes, there are too many.

      1. That’s interesting. As a long-time non-degreed self-educated software engineer, I always imagined having a PhD gave someone the advantage of having studied theory at a high level, which might be of real value in a practical engineering world. I have always respected the doctorate-holders I’ve worked with for their wider understanding of systems, underlying principles, and so on – it’s like they’ve been up to the mountain top and seen the Big View, while I’ve been clambering around in the underbrush learning what I can from the things right around me. In a certain sense, every software engineering shop is engaged in a kind of research, so having been involved in formal academic research isn’t a bad experience to have had. But that’s only me limited view!

        1. You can measure these things.

          What is the pay difference between someone who got a simple degree and someone who has a PhD?

          What I have read is that on an age-corrected basis (so comparing people who have the same age), PhD holders do not earn more. They may even earn less because they have less work experience.

          That is, who earns more… a 30-year-old engineer with 7 years of experience in industry… or a 30-year-old with no industry experience whatsoever but a freshly minted PhD?

          To this you must add that during their PhD, the PhD holders earned substantially less.

          Of course, there are benefits to having a PhD. But I submit to you that it is easy to overestimate the benefits outside academic jobs.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax