Skip to main content

Corporate sponsorship in Computer Science research

Luis von Ahn came up with a great idea to bolster research funding in an ailing economy -- corporate sponsorship of professors wearing logos while they teach. I wholly support this idea, especially since I currently wear t-shirts from companies like Microsoft, Amazon, and Intel for free. These companies really should be paying me for my advertising their brands to my students, given my ridiculously high degree of influence over them.

Add ImageThe recent New York Times article about drug company ties to medical schools got me thinking about why there isn't a similar controversy with corporate sponsorship of computer scientists. After all, many of us get research funding from companies, and much of that funding comes with an explicit (or implicit) assumption that we will leverage that company's technology in our work. For example, Microsoft gave my group a research grant last year to link our CitySense system into their way-cool SensorMap platform. This was clearly a blatant attempt by Microsoft to get us to use their technology, but how could we resist? We need the funding, and the only ethically dubious aspect of the project was having to program in C#. No pain, no gain, right? (Notice how I used the expression "way cool" in this paragraph? How's that for subtle?)

Apart from research grants, some companies grease us up with really serious perks! For example, Microsoft flies hundreds of CS professors out to Redmond every year for an intense three-day "Faculty Summit," the capstone of which is usually a cruise on Lake Washington with an open bar. Believe me, there is nothing that says "high roller" more than being crammed on a boat with a few hundred geeky CS profs drinking cheap chardonnay after a long day hearing talks about .NET and Windows Media Services. The coolest part is we get these really spiffy fleece vests to take home with us, which would be great for keeping warm in the New England winters except they have no arms. Those dermatologists getting free golf vacations to St. Kitts have no idea what they're missing!

It's clear that this flagrant corporate brainwashing is starting to trickle down to the educational mission as well. Hundreds of universities have ditched standard, non-proprietary languages like C and are now teaching their intro CS courses in -- gasp! -- Java. Here at Harvard, we're letting this nutjob from Sun named Jim Waldo teach a distributed systems course, knowing full well that he uses the entire semester to indoctrinate our students in how to program Java RMI. Stanford is even offering a course on iPhone programming. Both MIT and Stanford named their CS buildings after Bill Gates, and Berkeley named a lounge after -- get this! -- Steve Wozniak. What's next? The Werner Vogels Library? The Sergey Brin and Larry Page Annual Easter-Egg Hunt?

Where do we draw the line with this nonsense?

So I think there is a real crisis here and it's clear the NY Times is just not paying attention. I for one applaud those brave Harvard medical students who have dared to stand up to the insidious support of the drug companies with the expectation that rejecting corporate sponsorship will endow them with a "pure" education. It's only a matter of time before a bunch of CS students wise up to what is going on and do likewise. They may even go so far as to start a Facebook group to protest. Now that would really be something.


  1. You, Sir, have just made me spew coffee. Well played... well played, indeed.

  2. Nice article. Very thoughtful.


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…