Skip to main content

Top Prof

The success of reality TV shows that feature creative professionals in competitive situations has convinced me that it is time for a reality show for CS professors. Let me propose TOP PROF -- a new Bravo series featuring 12 junior CS profs all competing for the ultimate prize -- tenure at a top department, say -- in which each week one professor is voted out of the department until only one is left. The judges would include recent Turing award winner Barbara Liskov, the irascible but highly respected Andy Tanenbaum, industry bigwig and firebrand Al Spector, and (for comedic relief and 80's throwback cachet) the voice of WOPR from War Games.

Each week the contestants would have to face a different challenge that tests their ability to be the Top Prof. For example:
  • Review 25 conference paper submissions in 72 hours flat;
  • Prepare an undergraduate lecture on a topic you haven't seen since sophomore year;
  • Write a multimillion dollar grant proposal with six Co-PIs from three other universities in a week (and get all of the budget spreadsheets to work out!);
  • Juggle submitting 4 papers to the same conference, including one poorly written paper by a new grad student that requires a last-minute rewrite;
  • Write a dozen thoughtful recommendation letters for students you only saw briefly in your class three years ago;
  • Respond to hundreds of emails with no more than one-line responses; and
  • Hold a series of back-to-back half-hour meetings all day and manage to stay awake at the colloquium talk at 4pm.
I think this would do wonders to raise the stature of our field. Any volunteers?


  1. Matt, I love this. Especially since the bullet points are so true to life. I have done all of these things too, and in fact doing #2 this week!!

  2. I'd watch that show. Wait, can I try out to be one of the contestants?

    Can we also have a confession-cam where the theorists rip systems professors and vice versa?


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…