Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
61–70 of 174 posts
Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#62Always do at least 1 full rehearsal with a timer, preferably two full rehearsals where the first one you do keep a timer but also have a notebook (physical) present to quickly write down adjustments you want to make. Do a live demo, people love live demo's, but be prepared for when disaster strikes (it will), if possible run your live demo on a physical device with you during the presentation. Most places allow you t…
I'm not sure if I agree with that, in my experience they seem to fail or underwhelm about 50% of the time.
Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#63Something practical I haven't seen mentioned yet: unless you know the venue, assume the screen is far away from the audience (so the text needs to be large) and that it's hanging low (so most people can't see the bottom of the slides).
Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#64If you're being recorded for it to go on youtube, and you're doing a Q&A at the end, please repeat any questions that are asked for the benefit of the mic and those watching on youtube. Thanks
Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#65Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#66Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#67Know you're talking about. That alone will make the talk more natural, as you'll be able to adapt to your audience due to having knowledge outside of just your research. This was the biggest change between the presentations I had to give in high school and the ones in college and above. In high school, the topic was usually given to us, whereas in college and later, I got to choose the topic I was most knowledgeable…
To expand on that with "obvious" advice: Know your audience. Present accordingly. Are you an expert or a beginner relative to your audience ? If I'm explaining something technical, I might take a more assertive tone when glossing over details with a novice but speak with more deference to an expert. (e.g. Throw in a few "I think ..." or "My understanding was that ...") Getting a quick grasp of where the speaker is co…
Use this ance-data to shape your tone and phrasing.
Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#68Always do at least 1 full rehearsal with a timer, preferably two full rehearsals where the first one you do keep a timer but also have a notebook (physical) present to quickly write down adjustments you want to make. Do a live demo, people love live demo's, but be prepared for when disaster strikes (it will), if possible run your live demo on a physical device with you during the presentation. Most places allow you t…
> Do a live demo, people love live demo's It really depends on the topic of the talk. If it's something that can be demonstrated in a quick and straightforward way, do a demo by all means. But I've seen talks where people were forcing a demo into a talk about complicated concepts. There's little value in seeing someone type in a page of code, compile and run. Or seeing something run without understanding what is happ…
STYLE
> [slides] are not cue cards for the speaker
Personally I disagree with this point and have developed a presentation style I'm happy with based on the slides being my cue cards (average 5-10 presentations / year for the last 15 years).
I do NOT read the talk from my slides and can't stand it when speakers do that! But, each slide should jog my memory of everything I need to say at that point. Maybe I'm talking about some stats as background, fine, the slide should be a bar chart of those stats, or a map, or an illustrative photo. Rarely a list of bullet points, though I don't prohibit them altogether and will tend to conclude with a list of bullets to leave in the background as a summary while I take questions. Overall the slides should complement the talk, not be a duplicate. But they serve a second function of reminding me of all the things I need to say.
As a programmer you will appreciate the reason for this: I have cut the number of entities I have to process in my head from three (slides, audience, notes) to two (slides, audience). Keeping track of and having rapport with the audience is essential to me, even if that just means looking at people to see how engaged they are. With notes/memory in the equation I used to get a lot more nervous and not pay enough attention to the audience. Cutting out the notes allows me to focus on communicating better. It's a shared context, the audience can see exactly[1] what I can see.
If you're in sales then I see another tactic used instead, which is to memorize the talk so thoroughly that you don't need notes or presenter view. Fair enough. I'm an academic researcher; while they say all our presentations are a sales pitch on some level or other they clearly aren't expected to be as slick as "sales" sales. My constraints are having limited time to prepare, and wanting to stay natural. I do rehearse but I don't over-rehearse as I find that kills my own interest in the talk as well as taking more time. Usually the minimum for me is two full run throughs, probably stopping the clock multiple times during each to apply edits as I see fit (hopefully only a few edits second time).
HANDLING CONTEXT SWITCHES
The one exception to [1] is context switches. As others have said, finding the perfect words for the introduction to each new topic really helps get the flow going. These can be remembered, written on notes, written on slides, written on slide notes visible in presenter view, whatever.
I'm a big fan of presenter view, not for notes, but purely for the ability to see the next slide and introduce it slightly before the change. It helps to leave each slide knowing what direction you're going in so you're not surprised by the next one. I do worry slightly that I'm dependent on presenter view and turn up early at each venue to make sure I can get it working (not all of them can).
NERVES
Someone said don't drink too much alcohol. Based on my experience as a performing musician this is true :) Same goes for caffeine for the opposite reason, it really heightens the nerves. On the subject of nerves, just accept that some talks seem to go better than others. If you find yourself having a failure of confidence, take a deep breath and keep going. Easier said than done I know, but it always feels worse on the inside than it really looks; I have had people come up to me after talks where I thought I did awfully and tell me how engaging they found it.
AUDIENCE ENGAGEMENT
If you can find a way to further engage the audience without forcing it - quiz questions, polls etc - go for it. Quiz questions can help set context for a new topic. Despite my love of the material I've never really been a lover of talks and can get pretty bored in the audience, so I really appreciate this sort of thing.
Example: on a few of my talks lately I've showed a picture of some protestors up trees by a road, asking who can name the incident. (Protests vs Newbury bypass construction). Followed by more protestors and an airstrip (former US nuclear base Greenham Common). Most of my UK audiences will get these right. Finally I asked what links these two things. They may or may not get the latter: the success of commercial development on Greenham Common, when it ceased to operate as an airbase, was blamed for the failure of transport models to correctly predict the effect of Newbury bypass. Doesn't matter whether anyone guessed the final answer, which is obviously a bit specialist. The point is I've now got people thinking about the many interconnected elements of simulating transport which is a great intro to the topic.
Re: Ask HN: What are the things keep in mind while giving/preparing for a tech talk?
#69Best advice I had about giving talks (from a non-techie) was 'tell a story'. People like stories more than information. If they want information they can mine you for it afterwards.
Don't just tell a story. Use the tools of story telling. Have a three act structure (Setup, confrontation, resolution). Have a plot. Use foreshadowing. Use one of the common generic stories as a framework (Hero's journey, coming of age, etc). Make it personal - bring in either parts of the audiences life, or of yours. And close with a positive message You know when you were a kid, and you had that one funny relative…
Some people are good at wrapping tech talks into interesting stories. But they are very rare in my experience. If you don't have a story to tell, don't force it. Don't try to present everything as this grand idea that's related to everything you've done since childhood. It gets old really fast.
I've seen students take a course in speaking where they hammer into them this "three act structure". Invariably, the talks they give would be much better if they would just stick to the technology.