Skip to main content

Text and video of my OSCON 2011 Keynote presentation

I was unable to attend OSCON 2011 to give my keynote because of travel problems. The folks at O'Reilly were kind enough to let me have a five minute slot in which I presented via video. Here's the video and the script I was working from.

Alan Turing

A name we should all be familiar with.

Next year, Alan Turing would have been 100 years old, but he died woefully early aged 41. He is the father of computer science having described the Turing Machine: the fundamental computer that underlies the machines we use today. He is known for the Turing Test used to determine whether a machine can think. And his work during the Second World War breaking Nazi codes is celebrated at Bletchley Park.

His life tells a story of a brilliant man. But his death tells the story of how prejudice snuffs out potential. How discrimination hurts us all. His story is relevant today and relevant at this conference.

Alan Turing was gay at a time when homosexuality was illegal in the UK. He was prosecuted and given the choice of prison or estrogen injections. He chose the female hormones and grew breasts. Two years later, in 1954, he took his own life. What a loss. Just imagine all that this brilliant man could have done with a few more years of life, he had done so much in just 20 years.

In 2009, I petitioned the UK to government to apologize for the treatment of Alan Turing. To my surprise over 32,000 people in the UK signed the petition and on September 10 of that year then Prime Minister Gordon Brown called me at home to tell me that the apology text was being issued that night.

I harnessed this great crowd of ordinary people and celebrities by myself. Using a mixture of Twitter and Facebook and old fashioned press and television the word spread quickly. I have written about how I achieved this on O'Reilly Radar. The campaign grew slowly at first as only a small number of people in the computer world, who already knew about the Turing story, signed. But a big break came when The Independent newspaper wrote about the campaign and shortly after Richard Dawkins lent his name. As Twitter amplified stories in the press more and more people signed until the BBC decided to cover the story first on its web site and then on television.

With the weighty BBC story to tweet the petition quickly grew and got the attention of Downing Street. The petition itself was all managed electronically through open source software created by the British non-profit My Society. With an open source petition platform the British government has enabled direct, electronic democracy.

I originally planned to talk in detail about the apology campaign, but in recent days O'Reilly made an announcement that made me rethink this talk.

Last Sunday, Tim O'Reilly announced that a code of conduct for all O'Reilly's conferences would be introduced covering sexual harassment and other inappropriate behavior. That's wonderful, but as a community built on the ideas of openness, sharing and freedom we can do much more.

The prejudice that harmed Alan Turing may seem far from off color comments, offensive slideware or unwanted advances, but all these things end up with the same result: valuable people are discouraged from being part of the open source world. Open source has changed the world, let's continue "being the change we want to see in the world" (as Gandhi put it), by including everyone who wants to join us regardless of who they are.

Alan Turing and the other great minds at Bletchley Park were brought together because Winston Churchill ordered that no stone be left unturned in the search for the right talent. Whether Turing was gay, or another great mind was a woman, or of a particular religion, was irrelevant. What mattered was ability. From this great diversity came great strength and great progress.

Let's honor Alan Turing not just with a code of conduct, but with our code (for he would surely be happy to see so much software) and with our conduct.

Thank you.

And have a great conference.


Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of