Skip to main content

Talking to Porgy

If you're a computer programmer you might have found yourself describing a particular problem you are having to a colleague. Many times you'll never even finish the explanation, or get any feedback before you uncover the solution to your problem. I've found that a colleague is not even necessary: you can talk to anything as long as your verbalize your problem.

While working on my book I would frequently describe out loud the scientific sections I was writing to make sure that I understood what I was explaining. To feel a little less ridiculous I used to do this while talking to my cat. The cat didn't understand what I was talking about, or at least it never said a mumblin' word, but speaking aloud helped me enormously.

I also find myself talking directly to my computer while debugging. And there's something in speaking out loud a problem that makes cogs in my brain mesh and a solution propose itself.

In Coders a Work Joe Armstrong (who created Erlang) describes a similar situation with a "useless" colleague:

I worked with this guy who was slightly older than me and very clever. And every time I'd go into his office and ask him a question, every single question, he would say, "A program is a black box. It has inputs and it has outputs. And there is a functional relationship between the inputs and the outputs. What are the inputs to your problem? What are the outputs to your problem? What is the functional relationship between the two?". And then somewhere in this dialog, you would say, "You're a genius!" And you'd run out of the room and he would shake his head in amazement--"I wonder what the problem was, he never said".

Unfortunately, talking to animate objects is often seen, by the general public, as a sign of insanity. I only talked to the cat when the rest of my family were out of the house. But speaking out loud seems to be helpful because it forces you to explain clearly your problem, it forces you to find hidden assumptions, and it makes different bits of your brain work.

Since the thing you are talking to knows nothing of your problem you have to explain it clearly and in detail, as you go into detail you are forced to uncover parts of the problem you hadn't thought of. And, by speaking out loud you use the parts of your brain that form words, move your mouth, hear words and process them.

The Pragmatic Programmers call this talking to inanimate objects technique Rubber Ducking because they suggest placing a rubber duck next to your computer and talking to it. The Rubber Ducking page has stories of the different objects people to talk, and relates the story of a teddy bear at MIT that students were forced to talk to before bothering a member of staff.

The same sort of technique seems to have worked for Alan Turing. One of his nieces recalls Alan Turing having a teddy bear:

"It was called Porgy. He bought it for himself when he was an adult, and it used to sit in the chair when he was at Cambridge. He used to practice his lectures in front of Porgy."

The surviving Turing family were kind enough to send me a photograph of Porgy dressed in the little outfit that Alan Turing's sister made for it. You might like to print it out and post it near your computer. Next time you come up against a difficult problem, simply turn to Porgy and describe out loud the problem you are having. I'm sure Porgy can help.

PS. If you're on Facebook you can become a fan of Porgy here.


Mohan Arun said…
Just make sure noone else is watchin' as you pour out your problems to Porgy.
WOW Nice.

Popular posts from this blog

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 last name …

All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands. They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0image by Shinji
I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring):

The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30).
The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {
    float m = (360-30*float(h))*2/13;
    int s = round(60*(m-floor(m)));
    int col = h%6;
    int row = floor(h/6);
    draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1), r, h, floor(m…

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 informati…