I’ve had the good fortune to visit the Stanford CS department twice this week — on Monday I visited with some of the current section leaders to talk about Mozilla some, and last night I was on a CS careers panel with my very good friends Schrep & Mauria and got to see Mehran & Jay as an added bonus.
It’s been interesting to be back — both incredibly familiar and pretty foreign to me. [As an aside, I have different feelings when I engage with the d.school — I think maybe it’s because I’ve gotten more involved with Diego & Bob & George and design later in my life, and am increasingly interested in those sorts of problems — so I associate undergraduate CS education at Stanford with some exceptionally strong (and fond) emotions that come along with growing up in college.]
On the incredibly familiar side, I understood all the language; I recognized section leaders pulling a huge stack of papers out of their bags; using the time before the class to grade those programs; talking about whether something deserved a “check” or a “check plus.” I recognized the tiredness that comes from going all the time, but also the common fun & shared interest of the section leaders. And while I guess my time at Stanford pre-dated Joss Whedon, I even recognized the feeling when they all started talking about how much they love Dr. Horrible. And of course, of course, I remember looking forward and wondering what life in the world was going to look like, how I was gonna convince someone to give me a job I probably wasn’t really qualified for, and, really, what the hell people at work did with all their time.
On the unfamiliar side, holy cow these students know so much today, about so many things that are important. In 1995 when Bryan and I were both getting ready to start at Trilogy, I think we had a pretty good idea of what companies like Apple and Intel and HP did, but beyond that, not so much. But the students I talked with yesterday & Monday are incredibly informed. They understand the differences between Firefox & Chrome & Safari & IE, and even the implications of those differences. They understand how the Facebook platform works — many have written Facebook apps or web apps that are already in the world. And they understand more than I would have imagined about open source, which makes me hugely optimistic.
They asked lots of great questions. Some were super-specific, about things like what we’re going to do with Ubiquity over the next year, how we think about competition with Chrome, what it is, exactly that product managers do. (That last question I told them they’ll be asking for a pretty long time.)
But also things like how to decide what job to take? How to measure success? How much risk should I take right now? Does it matter if I do systems or AI or HCI?
And, of course, all of us older folks on the panel found ourselves saying things like “well, you won’t really get this now, but…” or “it took me 3 jobs to really figure out anything about that”. But the coolest thing, really, was that everyone on the panel agreed that the single most important thing was to not over-think it, to do what makes you engaged and interested — to do, in Tom Kosnik’s words, “things that make your soul sing.” And more importantly, to do things that matter to people, that change the world, that make things better. And even with all the economic doom around (more on that in my next post), that message of small groups of people getting together to change the world really resonated and made sense.
So with distance now, some things are clearer, some things not so much — that’s a characteristic of being human, I suppose. But I’m excited about this next group of people who are ready to change the world.