Knife Man

What I'll be doing in April ...

It appears that I've been accepted as a speaker for the 2005 O'Reilly Open Source Convention.

Gulp.

If software conferences interest you at all, this one is in Portland, Oregon, and when they make a call for volunteers, get your name in quickly and you'll get free admission.
  • Current Mood: accomplished accomplished
Dude. You're in cahoots with Bill O'Reilly now?

I see a LOT has changed since we last chatted... I better get to you before it's too late.
The icon is there because I confess that I'm a tad nervous about this. There are several directions I can take the talk, but I can't cover them all and I only have 45 minutes to show people that my topic is worthwhile (and it's kind of an esoteric topic for most programmers.)
Hah! Not for a minute. You're smart and engaging, and I know you'll be well-prepared. This is really exciting stuff, and a wonderful thing to add to your resume. Engagements like this do excellent things for your marketability.
My other tip is to avoid the structure of:

1. intro
2. history
3. background
4. something useful

and instead do:

1. something useful
2. explain the parts you had to gloss over
3. background, history, introduction

I learned this from TCP/IP Illustrated Vol 1 he doesn't start out explaining what an IP packet is, the history of the Internet, blah blah blah. He starts out with "Become root and type this command... I'll explain what it means later. The command is "tcpdump -n". Ok? great! Now open another window and ping the machine running TCPDUMP. You'll see something like blah blah blah. Those are THE PACKETS. isn't that cool? Awesome! Did you see ARP packets? Cool! Now turn to the next chapter and I'll explain what all that meant." It like a roller coaster ride and very exciting when you teach it that way.

My TIme Management class begins with "how to deal with interruptions without sounding like a jerk" then I introduce myself, talk about some principles, etc. etc. My "Massive Upgrades" talk starts with a walk-through of a real OS upgrade disaster, then builds up all the was we could have prevented it, etc.

Works for me :-)