the Communications Web site, http://cacm.acm.org,
features more than a dozen bloggers in the BLoG@CaCm
community. in each issue of Communications, we’ll publish
excerpts from selected posts.
Follow us on twitter at http://twitter.com/blogCaCm
DOI: 10.1145/1610252.1610257
http://cacm.acm.org/blogs/blog-cacm

CS Woes: Deadline-
Driven Research,
academic inequality

Jeannette M. Wing writes about the negative effects of deadline-driven research and Mark Guzdial discusses the role of computer science faculty in fostering inequality.

 

From Jeannette m. Wing’s “Breaking the Cycle” How can we break the cy- cle of deadline-driven re- search? In computer sci- ence, there has been a growing trend in the past decade or so for researchers to publish in workshops and confer- ences in order to increase the length of their publication list. This situation is especially true of junior faculty, worried about getting tenure; graduate students, worried about getting job interviews; and now even undergraduates, worried about getting into graduate school. In promotions and tenure committee meetings at some schools, discussion of the number of papers can overshadow discussion of the quality and impact of the candidate’s work.

We have successfully trained deans and provosts that, in computer science, papers in premier conferences count as much as or more than papers in journals. So, the pressure to publish in conferences is even that much more

intense. And presumably the more the better. To accommodate the research capacity of our field, new workshops and conferences (and journals) proliferate, resulting today in extensive Web sites maintaining double-digit rankings of conferences. It is now common practice to see the conference success rate included with each publication listed on a candidate’s résumé. (I will not repeat the cogent arguments that others have given on the subject of journals vs. conferences, published in Communications, 1–3 but they are relevant to this topic as well.)

We are now in a state where our junior faculty are mentoring graduate students with this deadline-driven approach to research. It’s the only value system they know and they are passing it onto the next generation. When one of my own graduate students, after we agreed that we would submit a journal version of our conference paper, said to me, “Jeannette, the author guidelines for Journal X don’t specify a page limit,” I knew something was very wrong

with our current culture in computing. We are now in a state where the common thought-chunk of research is a 12-month effort that fits in 12 pages.

We, as faculty advisors, are in a bind: Do we say to our student, “Yes, go ahead and submit to that conference [whose due date is looming]” or “No, don’t waste your time writing for that conference. Your work is not ready. Spend the time developing the work”? Do we give in to the peer pressure our students feel, making them potentially less competitive when they are on the job market? We need to promote a culture that encourages faculty and student researchers to take the time needed to work out their ideas so that when they feel ready, they can submit based on the import of their contribution.

Moreover, conservatism tends to win out in program committees, when submissions are competing for a finite number of conference slots, and in panel reviews for funding agencies, when proposals are competing for finite resources. This attitude leaves less room for the bold, creative, risk-taking, visionary ideas, especially those that are not fully fleshed out with all the i’s dotted and t’s crossed. Note that I have nothing against conferences: they are important for the expeditious exchange of technical ideas, as well as networking among researchers and between academia and industry. I have nothing against (high-quality) incremental research: some research agendas are long-term in vision, but rely on making progress step by step, building on prior research results.