Skip to main content

Welcome to Stephen Chong and Krzysztof Gajos

Last year was a huge success for faculty hiring at Harvard CS -- we added three new faculty members to our ranks, two of whom are starting this fall. (Yiling Chen started last year -- she works at the intersection of Computer Science and Economics.) Fortunately, we managed to do the search before the present economic unpleasantness; so I'm pleased to welcome Stephen Chong and Krzysztof Gajos to Harvard.

Stephen got his Ph.D. from Cornell and works in the area of programming languages and security. His work on the Swift system (published in SOSP'07) allows one to build secure Web applications where the client- and server-side code are automatically partitioned from a single, unified program written using the Jif variant of Java, which incorporates support for information flow in the programming model. This is a very practical approach to providing information flow support in a real system.

Krzysztof got his Ph.D. from University of Washington and is the first HCI person that we've hired at Harvard. Actually we've been looking to hire in this area for some time, but never found someone we really liked -- until Krzysztof. He is a great match for the kind of multidisciplinary work that we do here. Among other things, he developed the SUPPLE system, which automatically generates user interfaces for users with motor disabilities -- a nice combination of HCI and machine learning work.

Harvard grad students can look forward to the fact that Stephen and Krzysztof are both teaching graduate seminars this term.

(On a related note, I am delighted to have a new name-spelling challenge on my hands. It took me a couple of years to learn how to spell Mema Roussopoulos' surname without looking it up -- I am resisting the urge to create a macro for Krzysztof. This reminds me of my colleague from Berkeley, Rob Szewczyk, who once cheekily explained to me that his name is spelled exactly as it is pronounced.)


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…