Tech talks don’t have to be boring
billwadge.com
billwadge.com
I've given talks all over the world and many were highly rated, and I usually average 2 slides per minute. A 40 minute talk will have almost 80 slides in it.
> Everyone with functioning eyesight is a visual learner.
And also
> Eight is the maximum number of slides you should give in a talk, whether 20 minutes or 50 minutes.
So which one is it ? you want people staring at the same 12 slides over 50 minutes or you want to actually show them something ?
He does also argue for very simple slides so he's really almost arguing for not using slides at all other than to reinforce some specific points.
Dick Hardt’s presentation is at https://youtube.com/watch?v=RrpajcAgR1E&t=6s - the content has aged a little (though less than I expected before I just rewatched it) but if you’ve never seen it, I encourage you to watch it; it’s not that long, it will feel even shorter than it is because it’s so engaging, and it certainly illustrated to me how important communication skills are and improved my own presentation style.
Once you gain some experience, 4 is the only one I would say is a hard rule. Experience will teach you how to break all of the other rules effectively, as every other rule entirely depends on context. The main reason why tech talks are boring are two reasons - inexperienced presenters, and that engaging talks take time to prepare.
One tip I'll give for people is don't rely a script. If you have a script, you're writing emotion and adaptability out of it. Teaching content is a dance with the audience - you have to adapt to how they respond in order to present effectively. Give yourself an outline, and in your head run through twenty different ways you'd present that information to people. Knowing how to dynamically present your slides means you can engage with your audience far better and you can take time to read the room. If you present a talk twice, it should be different each time as the context changes.
I always write out a script before an important presentation. I number it with the corresponding slide numbers and read it out loud as I'm presenting. And now you're probably imagining falling asleep to the quiet droning of a disinterested high-schooler reading out loud in literature class, but that's only because most people never practice reading out loud effectively. I've practiced it a lot, and now my reading aloud sounds much better than me just speaking naturally. Practice it!
You're right that it's important to be able to adapt a bit, but usually that just means answering a question or two and getting back to the script, or skipping around the script a bit.
> 2 – Present at most 12 slides, no matter the length of the talk
The longer you sit on one slide, the more boring your presentation gets. Make hundreds of slides! Most should flow directly into the next (adding a single bullet, highlighting something else, emphasizing different parts of a visualization, etc.)
That "rule" is directly in conflict with rules 4.5 and 7:
> 4.5 – Visual, visual, visual
> 7 – No complex slides, whether text or images
You can't get by on 12 slides if each slide is supposed to be super visual but also not complex. Make 100!
factorials :)
Well, creating even a mediocre talk takes a LOT of effort. As a speaker, what do I get out of it? Presenting at anything "open source" almost certainly means I'm not getting paid for it. And, unless I can give a talk at least twice, I can't amortize the cost of it.
My two biggest problems in giving a tech talk are:
1) The audience is all over the map
If you give a talk about doing something in USB on Linux, some of the audience won't know what USB stands for. Some of the audience probably write driver code. This is a VERY difficult audience to communicate to.
2) Covering something meaty but not taking 3 hours.
Choosing USB on Linux again. To not take 3 hours, I have to dispense with the USB basics and launch directly into the specifics on Linux. Even that probably means that I'm talking about character devices on /dev that a lot of people have never dealt with. And after that, I can get down to talking about the cool thing that I actually wanted to talk about.
Yep. And lots of people don't pay attention to the difficulty rating which is usually there. (And what is there is often inaccurate--relative to what?)
I've given talks where I've simultaneously had feedback that the talk went over someone's head and that it was too high-level/fluffy.
The problem of the boring tech talks is that they demands a lot of attention (visual) but doesn't return enough stimulation. Your mind starts wandering without the enough stimulation/entertainment. So just give them less attention.
Not all the tech talks are good speaker, and not all tech topics are good fit for an entertainment. I'm fine to accept that fact and adjust how to consume them.
That's said, I hope there are more audio-focused tech presentations out there. If you know any good series or something, please let me know.
[1] https://open.spotify.com/show/5FGA58foRFkJ6IgJbCFYgm?si=tDKE...
[2] https://open.spotify.com/show/59I1XnvAB9fQzSj9SIKCoI?si=v58-...*
That doesnt mean you have to sacrifice information or rigor. But if excellent information is said and nobody was listening was it ever really said at all?
This. So much this. I can read, man. I can read while you're talking. I can read it faster than you can say it. So if you read the text, you're going to take longer than I am, and then I'm going to have to wait for X seconds while you slowly get around to finishing telling me what you've already told me. And every one of those seconds, you're losing more and more of my attention.
It will be the best 50 min investment you can make to make you a better presenter.
If you have something to say, write a blog post, make a short audio/video clip.
Going up on a stage and presenting is so yesterday. We have near infinite movies and tv shows to watch and we don't, because boring, and you expect to keep people's attention with your presenting-this-for-the-first-time-lol thing?
Get with the times folks - if you have something to say, just go ahead and say it in 30 seconds and give me a link to a 5 minute thing, that gives a link to a 30 minute thing. It's called the internet - you don't need to mimick presenting in front of a class - that was a necessary format due to limitations, not an ideal format because of how great it worked.
Both formats have their place, and often a talk is turned into exactly what you describe -- a blog post with a text description, a highlight reel, and the full talk (that you can watch at 2x speed if you really want to).
I get bored, however, by fluffy talks that have lots of memes and pictures and big text and anecdotes. In any reasonably complex actual tech talk, you'll have concepts that need slides with a bit of text and maybe even formula (or code), simply because the audience will sometimes get distracted or forget what you said a minute ago. I find that perfectly fine and better than the alternative.
So overall this seems to be advice for people who wish their tech talks were actually TED talks.
When people remember your preso, they'll remember the dog images, but those will all represent some meaningful take-away from the talk.
We're engineers, social intelligence isn't our specialty, but this is pretty easy to codify.
But collaboratively editing the videos would already be a step forward.
If only YouTube allowed us to write some plugins ...
If you are into Python, Raymond Hettinger and Brandon Rhodes is all you need.
Then, when I read the piece, most were already known to me.
One should watch the marvelous guide by Patrick Henty Winston- "How to Speak".
He also has a book called- "Make it Clear". I highly recommend this.
One general rule I give to speakers, and stand by it, is: take time to breath.
I don’t see proof of usability of this rules presented in article, so yeah, just arbitrary list, don’t mind it too much. Watch good standup, and learn presentation structure from those guys.
One example I have is Chandler Carruths talk in CppCon 2019 "There Are No Zero-cost Abstrations" https://youtu.be/rHIkrotSwcc Chandler presents his point clearly and goes deep enough into the subject.
GopherCon 2018: Kavya Joshi - The Scheduler Saga
these steps work well for making up the difference