On Science as Art

What do you know, man?  A stereo’s a stereo.  Art is forever!

— Cheech Marin, last line of Scorsese’s After Hours

We were having dinner the other night with Anusha Gummadi, the wife of a colleague of mine, and she asked me if I hoped my soon-to-be-born child would become a scientist. My kneejerk reaction was: “Hell, no! Science is what you do when you can’t get a real job — you know, as an artist.”

Now, although I was (as usual) being half-facetious, the immediacy and vehemence of my retort took me a bit by surprise. After all, I am a scientist, and I (mostly) really enjoy what I do. There are many excellent reasons to become a scientist: intellectual stimulation, impact on society, useful skill set offering increased chance of employment, etc. There are also excellent reasons not to become an artist, the most important one being that it is an extremely low-percentage occupation. Most artists, even the ones who are actually talented, barely manage to eke out a living. Only a very lucky few make a lucrative career in the arts, and in my experience there is only a weak correlation between success and talent.

And yet…I wasn’t entirely joking.

When I was a kid, I enjoyed math, but my heart was in the arts — music and film, primarily. If you had asked me what I wanted to do for a living when I was a teenager, I believe “composer” and “filmmaker” would have been at the top of the list. Indeed, when I was a pre-teen, I sang in the now-defunct New York City Opera Children’s Chorus (with a few bigger solo parts), and I also spent a lot of time tap-dancing. Some of my fondest memories as a child were taking the train up from Long Island to Manhattan with my mother, and then the subway down to the bowels of the New York State Theater in Lincoln Center, where we rehearsed La Boheme, Carmen, Tosca, and more in a windowless room with Mildred Hohner, the matriarchal coach of the children’s chorus. Or over to an underground loft space in Soho, where I learned about rhythm and jazz from the members of the American Tap Dance Orchestra. (I had my bar mitzvah there!) That loft space was only a few minutes’ walk from a bunch of arthouse theaters showing movies from everywhere in the world. My favorites were Film Forum and Theatre 80 St. Mark’s.

And yet I ended up as a professor in computer science. How did that happen? Well, I was good at song and dance, but not that good. And I never demonstrated any particular aptitude for what I really wanted to do, which was composition. I took piano lessons, but was too lazy to ever become proficient at the instrument. I enjoyed watching films and listening to music — the weirder, the better — but I didn’t have any particularly interesting ideas about films or music that I wanted to create. I wrote poetry, mainly in a sort of Dadaist vein, but I spent a lot more time thinking about what would be a good title for a movie/poem/whatever than what it would actually be about. In short, I was all style and no substance, and what little style I had had been more or less done to death in the 1920s.

So when I went to college (at NYU), I decided pragmatically to study math and computer science. I always loved math, computer science less so. I enjoyed the CS classes I had taken as a child and in high school, but they were pretty basic (literally: BASIC and Pascal programming). And I was very far from a computer nerd: my idea of fun, as I said, was singing, dancing, listening to weird classical music or offbeat films — definitely not hacking. Originally I just wanted to major in math, but my parents convinced me to study CS as well, mainly because it would improve my job opportunities.

Boy, was that a good call. I learned after a few years at NYU that (a) computer science was actually more interesting than I had thought, and (b) I was good at math, but not that good. I think what really hit point (b) home for me was when I ended up becoming friends with some Eastern European students (Yevgeniy Dodis and Ioana Dumitriu, among others), and they won the Putnam Competition (meaning they were top-5 finishers). For those who don’t know, the Putnam Competition is an annual North American undergraduate math competition. I don’t know how my friends prepared for it — all I know is that I got straight A’s in math, but when I took a look at past years’ Putnam questions, I had absolutely no clue where to begin. I’m sure if I looked at them now, I’d have the same reaction. Yevgeniy is now a professor in theoretical CS (crypto) at NYU, and Ioana is a professor in math at University of Washington. They are mathematicians, I am not.

As for point (a), I would credit two classes with getting me really excited about computer science. One was Alan Siegel’s graduate Algorithms course, which I took either in my first or second year of college. The other was Ben Goldberg’s graduate Programming Languages course, which I took in my third year. The Algorithms course was my first experience reasoning about programs mathematically (if not exactly formally). The PL course was my first experience with functional languages (SML and Scheme, and a little bit of Haskell). Both of these were truly eye-opening, and ultimately convinced me that I wanted to pursue graduate studies in computer science, studying PL or algorithms or both.

OK, fast-forward 18 years (I’ll discuss some of those years in a different post). I ended up doing research in programming language theory for a living. This has been incredibly rewarding, but clearly based on my answer to Anusha’s question, it’s not quite what I would choose to be doing if I could pick any career.

Well, join the club, Derek! Almost no one ends up living out their childhood fantasy. More to the point, I think there’s an extent to which I am living out my childhood fantasy.

What do I do? I get paid to think about whatever I want, so long as I eventually write my ideas up, convince a few of my peers that there is something exciting about the ideas, and then if I succeed at that, I have to present those ideas to an even broader audience in a talk at a conference. And thinking all by myself is really very tiring, you know, so I get to hire extremely bright people to think along with me, do most of the actual work for me, and then I get to help them figure out how to explain their hard work and their cool ideas to other people.

Basically, in cinematic terms, I get to be a cross between a screenwriter and an executive producer. This is pretty incredible. What science has done is to fix that core problem I had as a child when I was writing poems — all style and no substance — by providing the thematic content around which to spin interesting stories. And as a result, I’ve managed, pretty much accidentally, to make science work for me as a means of artistic expression, as an art form, or at least as close to an art form as I’ll probably ever get.

Of course you could argue that relatively few people who go into science end up becoming professors. This is true. However, the percentage is still far greater than the percentage of aspiring artists who make a career out of their art. (I don’t actually have any evidence to back this up: that would require too much actual science.)

This view of science as art pretty accurately reflects my perspective on CS research. Art can be simple or complex, art can be easy or hard to understand, but there should be something about it that touches you, something that is elegant, something distinctive. Similarly, a research paper can present a really simple and retrospectively obvious idea that anyone can make sense of, or it can present a challenging extension to a well-studied proof technique that only three people in the world understand — I’ve written papers of both sorts — but it should strive in either case to illuminate and inspire, to demonstrate an original and memorable way of thinking about the problem at hand. I would not say that I succeed in doing this all (or even most) of the time, but it is always my goal.

And this is what I look for when I read other people’s papers, too. Maybe it’s why I have such high standards, and a reputation for being a harsh critic: poorly written papers really bum me out. (Btw, this reputation is totally undeserved — for example, on a recent program committee on which I served, my average review score was one of the highest of any of the PC members.  Just saying.)

On the flip side, well-written papers bring me great joy. One that comes immediately to mind is the paper “Ribbon Proofs for Separation Logic” by Wickerson, Dodds, and Parkinson from ESOP’13. It presents a graphical (yet formally defined!) language in which to write separation-logic proof outlines, and the tool implementing this language produces gorgeous “ribbon proofs” of program correctness. Aside from being lucidly written, the paper lends a distinctive visual representation to the core ideas of separation logic. It’s a pretty literal example of science as art, and what can I say, it made me very happy.

Screen Shot 2014-12-31 at 6.21.09 PM

Anyway, getting back to my soon-to-be-born child and the important life lessons I hope to impart to them — umm, maybe I could misquote the Dread Pirate Roberts from The Princess Bride: “Have fun, kiddo. Create, explore, sleep well. You’ll most likely do science in the morning.”

Or even more simply: “As you wish.”

Advertisements

On the Four Children (Part 1: Afikomen vs. Teeth-Blunting)

My favorite part of doing research is explaining it to other people.  This is probably because it is something I think I am pretty good at.  Why?  Well, I often feel like I have a very small brain in comparison to the people I collaborate with, and I am in awe of the complex technical work they are capable of.  (Perhaps you think I am being disingenuously modest here, and I don’t mean to imply that I am not clever, but I can assure you that many of the people I work with are much cleverer than I am.)  So I have turned this limitation into an advantage: I figure that if I can figure out how to get my collaborators to explain what they are doing to me, then maybe, just maybe, we have a shot at figuring out how to explain it to everyone else.

So how do you take complex technical work and explain it to a broader audience?  There is no simple answer to this question, but let me tell you what I think is the most important general concept.  It is the concept of the “four children” from the Passover Haggadah.  Jews will know already what I am talking about, but almost no one else will.  Bear with me.

Passover is arguably the most important Jewish holiday and the only one that my secular Jewish family has celebrated regularly since I was a child.  On this holiday we remember the exodus of the Jews from Egypt, but in fact we do more than that: we meta-remember it.  That is, we spend a lot of time talking about how our ancestors remembered it, and how best to keep remembering it.

Now, there is a section in the Passover Haggadah (the book that we read on Passover) about the “four sons”.  (There is of course no earthly reason in the modern world for this story to be so male-centric, so we will get with the program and generalize here to the “four children“, as some progressive Haggadahs do.)  Like many aspects of the Passover Haggadah, this section is indeed very “meta”: it’s not about the Passover story per se, but rather about the act of explaining the Passover story.  In other words, it’s about communication skills!

Specifically, the “four children” passage is about how you explain the story of Passover to young people.  The point of the story is that you have to tailor your explanation of Passover to the person you’re explaining it to, and take into account what they are capable of hearing.  The same principle will apply to writing a paper or giving a presentation: you have to think about your audience.

The Haggadah depicts your audience in the form of four children to whom you are explaining the Passover story:

  1. The Wise Child: This is the kid who is totally into Passover, is excited to learn, already knows a lot, and wants to know more.  Or at least that’s sort of implied.  Actually, the kid asks you a fairly boring technical question, something like: “What are the laws and statutes that God has commanded you to follow?”  You answer them in a correspondingly technical and obscure way, by randomly bringing up the fact that one is not supposed to eat any dessert after the Afikomen.  (What’s particularly hilarious and ironic is that this is a terribly depressing answer.  The Afikomen is not like one of those little farewell bon-bons you get at the end of a Michelin-starred meal — no, it’s a dry, cardboardy piece of unseasoned matzah, which represents the Passover sacrifice, but which you do not want to be the last food you put in your mouth unless you fancy choking to death while singing “Next Year in Jerusalem”.  At my house, we specifically ate dessert after the Afikomen: teiglach, honey cake, chocolate-covered matzah, macaroons, you name it.  We would eat anything, quite frankly, to get rid of the taste of the damn Afikomen.  But then again, we had other priorities.  End of rant.)
  2. The Wicked Child: This kid is not buying into the whole Passover thing at all, and doesn’t understand what meaning Passover could have for them.  The kid asks you, essentially: “Who gives a shit?”  You “blunt his teeth” (marvelous phrase, that) and tell him: “I do, you punk.  I’m remembering what God did for me.  If you had been there, you ungrateful bastard, God would not have done anything for you!”  So there.
  3. The Simple Child: As the name suggests, this kid is kind of simple and asks a pretty dumb question, literally: “What is this?”  You give them the less-than-30-second elevator pitch about Passover.
  4. The Child Who Is Unable to Ask Questions: This represents a very young child, perhaps one who is not yet able to even speak or pay attention.  With this kid, you have to start the conversation.

[Below is a beautiful illustration by Siegmund Forst from the 1959 Haggadah shel Pesach.  Here, the wicked child (upper-left) is depicted as Leon Trotsky, and the simple child (lower-right) is depicted as an everyman smoking a cigar and reading the sports pages.  I swear this picture is highly reminiscent of certain audiences I have spoken before at conferences.]

four-sons

In case it’s not obvious, my above characterization of the “four children” is not 100% accurate, but it’s really not that far off.  There is a lot to be said about the four children, Talmudically speaking, such as the specific texts that are quoted in this passage of the Haggadah and why they are quoted, etc., which I am not going to do here.  But from my perspective, the most relevant thing is that the four children are a wonderful way of thinking about your audience.  I know that when I write a paper or give a talk, I think quite a bit about how I’m going to target my presentation to the different segments of my audience that these children represent.

Broadly speaking, the wise child represents your expert reviewers, your insiders, the people who really know a lot about your topic and will care about the technical details of your work.  The wicked child represents your detractors, the folks who don’t really care for your style of work or think the problem you’re pursuing is pointless.  The simple child represents people who are familiar with the goals of your broad research area, but are not up to speed on the latest research or the specific technical problem you’re working on.  The child who is unable to ask questions represents the rest of the world.

In my opinion, the “four children” are a fantastic analogy for the primary segments of your audience.  That said, I would not recommend following the specific prescriptions the Haggadah gives about how to talk to them.  In particular, it would be wonderful if you could just shower your expert audience members with all the boring technical details of your work (aka the “afikomen”), and if you could “blunt the teeth” of your wicked detractors, but in practice I don’t think this is the most effective communication strategy.

Why?  Stay tuned.

To be continued…