See it on Yahoo! Video. And more photos of the event on Flickr, too.

Good times.

Upon returning recently from a relaxing two-week holiday in Italy with my family, I found myself looking at an opportunity to join Chad Dickerson’s Yahoo! Developer Network team as a Product Manager. What a nice way to re-enter the real world after a break.

With a clutter-free mind, it took me about 2 seconds to figure out that this was my chance to do many of the things at Yahoo! that I’ve wanted to do since joining the company last year. And the chance to work closely with Chad again was a huge incentive.

He and his boss Bradley Horowitz have opened up several innovative and very successful paths for Yahoo! including the new open Hack Day. Watching the excitement around that event build, it’s obvious that there’s a lot more that can happen there. I’ll also get to work more closely with Jeremy Zawodny who has been a key evangelist and one of the most important voices for the company.

The idea of Yahoo! technologies opening up as services is picking up a lot of momentum. It’s an important opportunity that we have to get right, and we’re getting more organized to keep up with demand. We also have to listen more carefully to what people want from us. YDN is a great way to catalyze discussions amongst developers using Yahoo! services and to open up broader dialog with Yahoo! teams.

I’ve already started digging into the data that’s available, and it’s obvious that Yahoo! Developer Network is on a serious growth path. Site traffic is rising. The blog is buzzing. API keys are flying out the door. And more and more Yahoo! APIs are getting released and at increasing speed.

It’s a fascinating time to be here, and I hope I can help the company both reach and push its potential in this new role. Thanks, Chad.

After observing several Hack Day presentations and conducting a few screencasts of my own now, I think I’m seeing a formula for doing a 90-second demo.

No format will replace charisma. And charisma won’t make a bad demo good. But these guidelines might at least give the presenter a baseline. And I’m sure this will help people who are competing at Hack Day.

People can usually articulate more than two words per second without sounding like one of the Kingsmen, but that doesn’t leave any room for dramatic pauses or potential hiccups in the presentation. So, a good 90-second demo will probably come out to maybe 150 words.

What can you communicate in 150 words? Not much.

The meat of the demo obviously must consist of a walk-through, but it’s often the beginning and end that screw up the whole thing.

The most common mistake is a poorly balanced intro that either drags on too long and makes the audience anxious or one that is too short and forces the audience to contextualize things in their own heads when they should be following what you’re saying.

Spend little or no time introducing yourself. Save that for the end. But spend 20 seconds defining the problem. Answer these questions:

1. What’s wrong or broken?
2. How do people deal with this problem today?

Then get to the meat. Step the audience through a story one click at a time. Show a screen. Explain what is being shown. And then describe what will happen next. Tell them where you plan to click or what action you’re going to take and then do it. Explain the result and then repeat, one action at a time.

If at all possible, build the story to a climax. Each step from click to click should get progressively more interesting. At least point out the less dramatic elements of the demo first and build to the most exciting ones at the end. At about 80 seconds, you want to reveal the POW that will get everyone clapping.

If you get your POW before 80 seconds, great. Crack a joke and get off the stage. Don’t drag it out if you’re already done.

If all goes well, eyes will light up and cheers will wash over you.

Finally, close with some kind of contact information. Announce your name and the name of your demo during the applause, and leave before the applause finishes.

Here are a few hints that might also help:

• Script it. Write out what you plan to say. It will take you about 10 minutes, and then have someone read it out to you so you can hear it for yourself.
• It’s never a waste of time to deliver a one-liner that will get laughs. If you have something funny to say, say it, without hesitation. Humor wins fans universally and buys you a fully engaged audience.
• The result of working code is often what presenters are most proud of, and there’s a tendency to go from intro to result too quickly. The audience wants to get inside your head and follow your thought process. If there isn’t an actual clickable demo to show, then walk the audience through a couple of visual diagrams that show what is happening behind the scenes.
• Make it big. The demo screen is never big enough, so change your screen resolution to be as big as possible without completely distorting the demo.
• Point to things on the screen with your finger. Don’t assume people are following your mouse. Stand in front of the screen and reach with your finger to show them what you’re talking about.
• Use dramatic imagery even if it isn’t technically correct or specifically relevant. Particularly when getting mixed in amongst a bunch of other demos, you want to burn a visual image into people’s memories. Nobody will remember a word you said, but they will all remember what it looked like.
• If your demo fails, don’t sweat it. It happens all the time. Be gracious and tell your audience how they can reach you to talk about your idea and perhaps see a demo later.
• Don’t pretend like a failing demo is going to come back “any second now”. Demo audiences are forgiving, but they’re rarely patient.

There are lots of common public speaking tactics to take with you on stage, too, but I would never proclaim to be an expert in that.

Those who can’t do, teach.

Lastly, here are some interesting resources on presenting:

1. How To Get A Standing Ovation, Guy Kawasaki
2. Behind The Magic Curtain (Doing demos with Steve Jobs), Mike Evangelist
3. 10 Tips for Successful Public Speaking, Toastmasters.org
4. Presentation Zen blog, Garr Reynolds
5. Wikipedia: Public Speaking

One of the more interesting hacks at Yahoo! Hack Day last week was a game that challenged the notion of tagging.

How effective is tagging for recall? Can you remember what you tagged any given item? This question gets right to an important issue.

del.icio.us was invented as a type of bookmark manager. Joshua Schachter needed a way to save web pages, and the tag format seemed like a better metaphor than folders for recalling things.

When I first heard about del.icio.us from Jon Udell, my initial reaction to the idea of a bookmark manager was very negative. That reaction was clearly related to this question, as I was sure then and just as sure today that my mother will never organize her web pages with tags.

(Actually, that’s a risky statement. My mother is so organized that she can locate my primary school grade reports as quickly as she can find her most recent ATM receipt. She may actually become a super tagger some day.)

The act of tagging for the purpose of saving items for later is not for everyone. It is perhaps only necessary for a small group of people in specific circumstances. Bradley Horowitz’s influencer pyramid is a great visualization of how tagging can add value for the rest of us. At the top is the person who makes extra effort to evaluate, filter, categorize and socialize things. This is the person everyone who wants something socialized on the Internet needs to talk to.

In my mind, tags are hugely valuable. They expose important meta data at an abstraction level that was previously hidden in the Internet user interface. They are connective tissue allowing data sources to talk to each other in meaningful ways. And human-edited tags can balance the inaccuracies of machine automation that happens in any indexing exercise.

What’s missing from the tagging world is automatic learning. People shouldn’t have to find the ’save’ button, click it, fill in tags, and hit save. My browser history says a lot about what interests me. The time I spend on a page says a lot about what I value. Any social activities I initiate or receive can inform a machine what the world around me thinks about.

The influencer is clearly willing to work harder to ensure information flows through the Internet in sensible ways, but everyone else will need something more personal to happen as a result of tagging to warrant the amount of effort to do it.

The introduction of tagging into the Internet user interface was a key step in the evolution of the medium, but the process of adding and collecting tag information needs to evolve before the effects of the tags will reach their true potential.

Last week’s Yahoo! Hack Day was, as usual, an eyeopener. In addition to the creative hacks, I was hugely impressed that the co-founder of the company and CFO among several other key executives spent an uninterrupted afternoon watching and then judging all the hacks.

Photo: Yodel Anecdotal

The only other model for bridging the gap between top brass and ground troops that I’ve seen work successfully was at IDG when founder Pat McGovern conducted his annual handshake around the world during the holidays. He meets with every single employee of the company (2k plus), shakes hands, chats for a few minutes and, if available, hands the employee his or her bonus. He remembers impressive details from previous conversations and clearly challenges himself to make a tangible connection with each person’s contribution.

Everyone admits that it creates awkward moments, but the effort is appreciated by all and wins him both loyalty and credibility across the whole company.

At Hack Day, I expected Jerry Yang and Sue Decker to spend much of their time on their phones while engineers were working their hardest to impress the crowds. Admittedly, I didn’t make it through the whole afternoon undistracted, but the judges were engaged in every presentation that I did see. No doubt they were paying attention and learning things that will impact their future decision-making.

There’s always the question of whether the hackers are motivated more by peers or by bosses. In either case, the 90-second demo format is the closest thing software development has to the clean and jerk. I’m not sure I’d call it chest-thumping exactly, but don’t believe for a second that every hacker doesn’t hope to beat his colleagues with the better hack.