I’m jealous of my students in many ways, for the things they’ll get to build and experience. But they should be jealous of me, too.
It was graduation week last week, which is always a great bash. The students enjoy it, obviously — but it’s mainly an event for the parents, many of whom are seeing their first child, or even the first child in their extended family, succeed at university. It’s also the time of year when we conduct post mortem analyses of what and how we’ve taught throughout the year, and how we can change it for the better in the next session.
One of the modules I teach is for second-year undergraduates on data structures, algorithms, applied complexity and other really basic topics. It’s a subject that’s in serious danger of being as dry as ditchwater: it’s also extremely important, not only because of it’s applications across computer science but also because it’s one of the first experiences the students have of the subject, so it’s important that it conveys the opportunities and excitement of computer science so they don’t accidentally nuke their lives by going off to do physics or maths instead.
One of the aspects of making a subject engaging is appealing to the students’ backgrounds and future interests — which of course are rather different to the ones I had when I was in their position 25 years ago. (I initially wrote “quarter of a century ago,” which sounds way longer somehow.) So what are the experiences and aspirations of our current students?
Many get their first experience of programming computers with us, but they’re all experienced computer users who’ve been exposed to computers and the internet their entire lives. They’re the first generation for whom this is true, and I don’t think we’ve really assimilated what it means. They’re completely at home, for example, in looking up background material on Wikipedia, or surfing for alternative sources of lectures and tutoring on YouTube and other, more specialised sites. They can do this while simultaneously writing email, using Facebook and replying to instant messages in a way that most older people can’t. They’re used to sharing large parts of themselves with their friends and with the world, and it’s a world in which popularity can sometimes equate with expertise in unexpected ways. It’s hard to argue that this diversity of experience is a bad thing, and I completely disagree with those whom have done so: more information on more topics collected from more people can only be positive in terms of exposure to ideas. For an academic, though, this means that we have to change how and what we teach: the facts are readily available, but the interpretation and criticism of those facts, and the balancing of issues in complex systems, are something that still seem to benefit from a lecture or tutorial setting.
Many of the students have also built web sites, of course — some very complex ones. Put another way, they’ve built distributed information systems by 17, and in doing so have unknowingly made use of techniques that were at cutting edge of research less than 17 years ago. They expect sites to be slick, to have decent graphics and navigation, to be linked into social media, and so forth. They’ve seen the speed at which new ideas can be assimilated and deployed, and the value that information gains when it’s linked, tagged and commented upon by a crowd of people. Moreover they expect this to continue: none of them expects the web to fragment into isolated “gated communities” (which is a fear amongst some commentators), or to become anything other than more and more usable and connected with time.
I’m jealous of my students, for the web that they’ll have and the web that many of them will help to build. But before I get too envious, it’s as well to point out that they should be jealous of me too: of the experience my peers and I had of computers. It’s not been without impact.
One of the things that surprises me among some students is that they find it hard to imagine ever building some of the underpinning software that they use. They can’t really imagine building an operating system, for example, even though they know intellectually that Linux was built, and is maintained, by a web-based collaboration. They can’t imagine building the compilers, web servers and other base technology — even though they’re happy to use and build upon them in ways that really surprise me.
I suspect the reasons for this are actually embedded into their experience. All the computers, web sites and other services they’ve used have always had a certain degree of completeness about them. That’s not to say they were any good necessarily, but they were at least functional and usable to some degree, and targeted in general at a consumer population who expected these degrees of functionality and usability (and more). This is radically different to the experience we had of unpacking a ZX-80, Acorn Atom or some other 1980’s vintage home computer, which didn’t really do anything — unless we made it do it ourselves. These machines were largely blank slates as far as their functions were concerned, and you had to become a
programmer to make them worth buying. Current games consoles criminalise these same activities: you need permission to program them.
It’s not just a commercial change. A modern system is immensely complex and involves a whole stack of software just to make it function. It’s hard to imagine that you can actually take control all the way down. In fact it’s worse than that: it’s hard to see why you’d want to, given that you’d have to re-invent so much to get back to the level of functionality you expect to have in your devices. As with programming languages, the level of completeness in modern systems is a severe deterrent to envisioning them, and re-building them, in ways other than they are.
Innovation, for our students, is something that happens on top of a large stack of previous innovation that’s just accepted and left untouched. And this barrier — as much mental as technological — is the key difference between their experience of computing and mine. I grew up with computers that could be — and indeed had to be — understood from the bare metal up. One could rebuild all the software in a way that’d be immensely more challenging now, given the level of function we’ve come to expect.
This is far more of a difference than simply an additional couple of decades of experience with technology and research: it sits at the heart of where the next generation will see the value of their efforts, and of where they can change the world: in services that sit at the top of the value chain, rather than in the plumbing down at its base. Once we understand that, it becomes clearer what and how we should teach the skills they’ll need in order best to apply themselves to the challenges they’ll select as worth their time. And I’ll look forward to seeing what these result in.
Congratulations to the graduating class of 2011. Have great lives, and build great things.