Thursday, April 29, 2010

Why I am a Computer Scientist

As a counterpoint to my last, somewhat pessimistic post on the future of CS, I thought I'd post something more upbeat today.

Ed Lazowska from UW gave the colloquium at Harvard this week on Computer Science: Past, Present, and Future. This is a talk he has no doubt given many times at many places, though it was the first I had heard it, and it was fantastic. More than anything else, his talk reminded me of why I am a computer scientist, and of how many great problems we have to work on in this field. I can't imagine wanting to do anything else.

Ed's talk started off reviewing what computer science has accomplished in the last 40 years, since the ARPAnet came online in 1969. This New York Times story from 2009 reported on the "Top 20 inventions of the last 30 years" and nearly all of them are derived from computer science in one fashion or another -- the Internet, PC, mobile phones, and email top the list. Although there's no surprise here at all, it was a great reminder of how much impact computing has had on nearly all aspects of the modern world.

This is why I am a computer scientist: because I want to change the world. Computing is the engine that is driving innovation in every field of humanity, and working on computer science puts you at the center of it. Of course, it's easy to forget that on days when I am beating my head against some obscure Objective C type mismatch bug, so it's nice to get a reminder of the bigger purpose.

This is why I am a computer scientist today, but it's not how I got started. My first experience with a computer was sitting down at an Apple II+ (I am dating myself) when I was 8 years old. I remember it clearly: The teacher told me to type my name at the prompt and I got:
]MATT
?SYNTAX ERROR
This was probably not the most rewarding first experience with a computer, but it taught me that this box spoke a different language, and I wanted to learn how to communicate with it. It was not long before I was writing BASIC programs to do lo-res graphics. While most kids in the class just manually translated their static image from a sheet of graph paper into a series of PLOT, HLIN, and VLIN commands, I was writing animated scenes (one was the pyramids with an animated sunset behind them) and even a sword-fighting game with a simple AI algorithm so you could play against the computer (keep in mind this was 3rd grade). I was totally hooked.

At that age, computers represented this amazing magical box that you could control and make it do almost anything. The games I was writing back then rivaled what I could buy in the store, but for me it was much more about writing the code than playing the game.

Now that I have a son, I wonder what his experience with computing will be like, and whether he'll be as turned on as I was by the whole mystery of the thing. Perhaps he will just treat the computer like any other appliance, like the dishwasher or telephone -- not something to be taken apart, programmed, explored. One thing we already do is play with the iPad, and even at 9 months old he loves to touch the screen and manipulate objects on it -- there are a couple of good iPad and iPhone programs for babies and the touch screen interface has tremendous potential there. But will he want to program? And how will he even do it? BASIC and LOGO were great back in the day as you could dive right in. I'm pretty sure I don't want to throw Visual Studio at him -- hopefully there are still good kid-friendly programming environments out there. And of course, the programs he'll be able to write won't be able to hold a candle to whatever the latest 3D immersive video game system he'll be playing then, so it's hard to say whether he'll appreciate the potential for doing it himself.

I am convinced that giving kids this very direct and rewarding experience with computing is important, though. If we turn computers in to just another kind of media consumption device (which most already are) then we'll lose that opportunity to hook the next generation.

8 comments:

  1. So, I'm not sure about computing environments built for infants, but MIT's Scratch is a great environment for the young elementary student. I highly recommend it.

    ReplyDelete
  2. I'm not sure about that claim that as a 3rd grader you wrote games that rivaled what you could buy. Maybe you forget that you could buy Ultima I and II, Microsoft's Flight Simulator, and the unimaginably awesome Pinball Construction Set for the Apple II, or maybe your parents hid this from you :-)

    You would have to have been a 6502 assembly-hacking 3rd grader to compete with these games. Quiz: what does "call -151" do?

    On the larger point, yes, I think there is a problem. Every year the CS freshman in my not-top-50 public University know less programming. They consider HTML and PowerPoint "advanced programming". But, they sure know how to facebook and youtube!

    OTOH, I think they still know more about programming than freshman Civil Engineers know about statics, so we'll just have to learn from the CE, ME, ChemE, and EE profs.

    ReplyDelete
  3. Actually, my 6th grade science fair project was on 65c816 assembly language programming. I wrote a mouse based paint program. Unfortunately I lost to a guy whose parents built him a "rail gun". Anyway, on the VIC-20 the games were not so good as those you mentioned. It wasn't for a few years after that that I got a hand-me-down Apple //e and years later in high school I got an IBM PC.

    Call -151 enters the machine code monitor, but I had to look that up :-)

    ReplyDelete
  4. @anonymous: you forget that only a very, very, very tiny fraction of the games from that time were of the quality level of Ultima, Flight Simulator, or Pinball Construction Set. Most games were certainly rivaled by what any of us could produce at the time :)

    ReplyDelete
  5. Hi, I enjoyed your posting. My son who is now 13 picked up Roblox. I don't know how he found it, but he learned many basic programming concepts from it. It is an open source platform so kids learn by looking at what others did.

    ReplyDelete
  6. Those pesky IEDs! Every weekend I have to waste several hours clearing them out!

    ReplyDelete
  7. Fascinating. I'm nostalgic about the old days of BASIC and LOGO!

    And I'm really impressed that you wrote any kind of game in 3rd grade, wow!

    ReplyDelete