TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: What are the things keep in mind while giving/preparing for a tech talk?

299 pointsby scarecrowxalmost 7 years ago

86 comments

akdasalmost 7 years ago
Know you&#x27;re talking about. That alone will make the talk more natural, as you&#x27;ll be able to adapt to your audience due to having knowledge outside of just your research.<p>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 about. The latter meant I was more passionate, more able to answer audience questions and more able to tailor the delivery to the audience.<p>One piece of advice I heard was that if you absolutely have to talk about a topic you&#x27;re not familiar with, talk about being a beginner in that topic. Talk about your perspective as an outsider learning that topic in the first place.
评论 #17564828 未加载
评论 #17564832 未加载
framebitalmost 7 years ago
A little bit of stage fright is generally healthy. It shows that you care enough to be concerned and you&#x27;re not getting too cocky. That&#x27;s an old lesson I learned doing (of all things) middle school acting class and it&#x27;s proven itself to be true over and over again.<p>Think about your slide and presentation style. For example, I have enormous decks for most of my talks (think like 55 slides for 30 minutes) but I burn through them very quickly, usually less than 20 seconds per slide. I came from film editing before moving to software so I approach my Powerpoints like a movie, it&#x27;s just my nature. Others have really short decks that are information dense so the emphasis is on the talking part of the talk and the slides just provide a reference in the background. Others forego slides in favor of straight-up demos, which is certainly slick if you can pull it off (high risk, high reward) and need little pictorial illustration.<p>Use the old 5 paragraph essay rules from high school as a starting point for structuring your talk: tell you&#x27;re audience what you&#x27;re about to tell them (thesis, topic, core argument) and how you&#x27;re going to tell them (outline), then tell them (supporting paragraphs), then tell them at the end again what you told them and how you told them (conclusion, restating your intro).<p>Humor helps, generally. This isn&#x27;t supposed to be a standup set so definitely don&#x27;t go overboard, but it can really help. Particularly if you can tie it in with some empathy for your audience. (&quot;We&#x27;re gonna do this in Perl. I love writing Perl, you just hold shift and smash the number row for awhile.&quot;)<p>And for heaven&#x27;s sake don&#x27;t read your slides.
评论 #17567496 未加载
评论 #17566675 未加载
评论 #17567911 未加载
评论 #17566955 未加载
gnuralmost 7 years ago
Always 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.<p>Do a live demo, people love live demo&#x27;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.<p>Most places allow you to have 2 devices connected, or quickly switch the HDMI cable to the demo machine.<p>Do not use a linux machine, I know this sounds harsh, but with all the types of beamers&#x2F;screens out there, a windows or mac machine will just have a much higher success rate. (I learnt this the hard way, in the end I could choose between mirrored 640*480 or full hd on the beamer only, which makes live demos much harder).<p>Create short slides, the slides are there to guide you and the audience. Try to prevent reading the slides out loud.<p>Use images and videos, they can tell more then a thousand words.<p>I often use the STAR approach to tell my story, this helps structure your talk. You don&#x27;t need to follow star exactly, but if trying to explain something, it often helps to first give a bit of background why you did what you did.<p>Make sure you let the audience know if and when you will be answering questions, some talks really benefit from interactivity, but if you are short on time, let people know they can ask their questions later (perhaps add a slide at the end with sources and your contact information).<p>Also, relax, the audience has already decided they want to listen to your presentation.
评论 #17564934 未加载
评论 #17564589 未加载
评论 #17564703 未加载
评论 #17564892 未加载
评论 #17564845 未加载
评论 #17564805 未加载
评论 #17574643 未加载
评论 #17570225 未加载
评论 #17564843 未加载
评论 #17564846 未加载
评论 #17564654 未加载
评论 #17564993 未加载
joshfraseralmost 7 years ago
People decide in the first 10 seconds whether they&#x27;re going to listen to you or use your session to catch up on email. So make your intro good. Catch their attention. Surprise and intrigue them. Memorize and practise your intro over and over again so when you walk on stage you can get comfortable without having to worry about the specific words you&#x27;re saying. Memorize your conclusion too so you can bring it home with a strong call to action (bonus points if you tie it back to your intro!). People remember the first and last things you say the most, so make those words count.
评论 #17565162 未加载
评论 #17565602 未加载
评论 #17566237 未加载
评论 #17568328 未加载
TeMPOraLalmost 7 years ago
Lots of good advice here. I&#x27;d add:<p>- Ask yourself what is your <i>real</i> goal of the talk. Are you trying to teach people something? Or are you making a live-action advertisement for a product&#x2F;service (or for yourself)? Optimize your talk ruthlessly for that goal.<p>- If you&#x27;re doing a talk in front of a small audience (say, 30 or less people), and you&#x27;re going to discuss details of code or charts presented on slides, then put all those code snippets and charts you want to discuss in a single document and give everyone a printout. A printed document has much higher resolution and quality than a slide (especially for the people sitting in the back), and will allow them to look back (or forward) at an important figure if you&#x27;re currently showing another slide. Paper is cheap and quite ecological, so don&#x27;t worry about that.
cedalmost 7 years ago
From Richard Hamming:<p><i>When I first started, I got practically physically ill while giving a speech, and I was very, very nervous. I realized I either had to learn to give speeches smoothly or I would essentially partially cripple my whole career. The first time IBM asked me to give a speech in New York one evening, I decided I was going to give a really good speech, a speech that was wanted, not a technical one but a broad one, and at the end if they liked it, I&#x27;d quietly say, ``Any time you want one I&#x27;ll come in and give you one.&#x27;&#x27; As a result, I got a great deal of practice giving speeches to a limited audience and I got over being afraid. Furthermore, I could also then study what methods were effective and what were ineffective.<p>While going to meetings I had already been studying why some papers are remembered and most are not. The technical person wants to give a highly limited technical talk. Most of the time the audience wants a broad general talk and wants much more survey and background than the speaker is willing to give. As a result, many talks are ineffective. The speaker names a topic and suddenly plunges into the details he&#x27;s solved. Few people in the audience may follow. You should paint a general picture to say why it&#x27;s important, and then slowly give a sketch of what was done. Then a larger number of people will say, ``Yes, Joe has done that,&#x27;&#x27; or ``Mary has done that; I really see where it is; yes, Mary really gave a good talk; I understand what Mary has done.&#x27;&#x27; The tendency is to give a highly restricted, safe talk; this is usually ineffective. Furthermore, many talks are filled with far too much information. So I say this idea of selling is obvious. </i><p><a href="http:&#x2F;&#x2F;www.cs.virginia.edu&#x2F;~robins&#x2F;YouAndYourResearch.html" rel="nofollow">http:&#x2F;&#x2F;www.cs.virginia.edu&#x2F;~robins&#x2F;YouAndYourResearch.html</a>
sramsayalmost 7 years ago
I have given many, many talks -- from dense technical presentations to generalized keynote addresses -- and have been doing it for over twenty years. Here, in my opinion, is the deal:<p>1. Don&#x27;t start your talk by apologizing. &quot;Well, first I need to apologize. I&#x27;m insanely jet lagged, and so I&#x27;m not sure how coherent this is going to be.&quot; &quot;First, I&#x27;d like to apologize. This is actually a revised version of a talk I gave in 2009.&quot; &quot;Let me start with an apology. I have a terrible head cold.&quot;<p>Just stop. If the talk is incoherent, you&#x27;ll just have to do your best on the spot. If you&#x27;re tired, too bad. If you think people might have trouble hearing you, say so. But don&#x27;t <i>apologize</i>. People do this because they&#x27;re nervous, not because the audience has been insulted or aggrieved in some way, and while it might seem like a friendly gesture, it&#x27;s more likely to communicate that you&#x27;re unprepared. Or nervous. And it&#x27;s a cliche.<p>2. Do not ever go over time. In fact, go under time. As Edward Tufte once said, &quot;No one ever left a presentation wishing it had gone on for another 45 minutes&quot; (or something like that; you get the point).<p>3. Do not read your goddamn slides to the audience. Please. That is not &quot;giving a talk.&quot; You can maybe do that if it&#x27;s a long quote, but don&#x27;t read the bullet points that everyone can clearly see right in front of them. Expand on them, provide counterpoints to them, whatever, but do not read them. If you&#x27;re thinking of your slides (when you&#x27;re creating them) as &quot;what I&#x27;m going <i>say</i>,&quot; you&#x27;re probably doing it wrong.<p>4. Use a laser pointer sparingly or not at all. Use it only to make a precise gesture necessary to point something out very specifically on a chart or map, and then shut the thing off. Making dizzying circles around every bullet point is incredibly annoying.<p>5. &quot;Never mind the mic. Can everyone here me? I&#x27;m just going to speak loud.&quot; Unless you&#x27;re very experienced with this (professional teacher, actor, or something like that), you probably don&#x27;t know how to project your voice for twenty minutes. Get the mic fixed and use it. If the mic can&#x27;t be fixed, speak way louder than you think you have to (without shouting). This is a learned skill, and most people don&#x27;t know how to do it (but think they do). If the venue is large enough to require amplification, it&#x27;s there for a reason.<p>6. Speak at a moderate pace. People speak fast when they&#x27;re nervous. The proper pace will feel a bit slow to you, but perfectly natural to the audience. Check yourself periodically. Write it down on your notes. Slow down.<p>7. If some parts of the information you&#x27;re trying to communicate are very dense or there&#x27;s some useful data that will help to contextualize your presentation, create a handout. Do not try to cram it all into a slide.<p>8. Take some time to try to imagine every conceivable question you might get in the Q&amp;A. You won&#x27;t hit them all, and things do come out of left field, but you don&#x27;t want to be caught totally off guard. Just review any common misconceptions or objections to what you&#x27;re saying, and give some thought to how you&#x27;re going to respond. Some people just want to comment. Thank them, briefly offer a comment if appropriate, and move on.<p>9. If you feel the need to ask a question like, &quot;Does everyone know what a frubazzle is?&quot; don&#x27;t. If the question is warranted, then you can be absolutely sure that someone in the audience doesn&#x27;t know what that is. Just say, &quot;Some of you may not be familiar with the term, &#x27;frubazzle.&#x27; A frubazzle is a . . .&quot;<p>10. Commit to getting better and better at it. When I gave my first talk (in grad school), I thought, &quot;It&#x27;s going to be really embarrassing when I faint dead away in front of all these people,&quot; and I made a lot of mistakes. Today, I have only the slightest pang of nerves when I step up, and it goes away immediately. When you hear a good talk, try to figure what made it good. How did the speaker behave? How were the slides set up? Did they do anything that you can incorporate into your own presentation &quot;style?&quot; Public speaking is an ancient art, and you need to treat it as you would the art of writing or the art of coding: with care and study.
boyteralmost 7 years ago
You don&#x27;t have to help people get from A-Z. Quite often they don&#x27;t even know where to start so going from A-D is enough. Know your audience in advance though.<p>Remember to pause and speak slower. It gives the impression you are really considering what you are about to say next and allows you a break.<p>Don&#x27;t drink alcohol before the talk (unless you need a shot to calm your nerves) and do have a bottle of water available as your mouth will most likely become dry.<p>Lastly relax. The audience is unlikely to call you out unless you make a total hash of it and they usually want you to succeed.
评论 #17574685 未加载
mhandleyalmost 7 years ago
Remember you&#x27;re telling a story. Think hard, before you start with slides, what that story actually is. Continuity and flow really matter.<p>Usually the first part of the story of a tech talk explains what the problem is. Many tech talks fail because the audience either doesn&#x27;t understand the problem, or doesn&#x27;t believe your problem needs solving. Think carefully who your audience are, and ensure you explain the problem in enough detail that you connect with your audience.<p>The middle part of a tech talk then is usually spent on explaining your solution to the problem. If you&#x27;ve explained the problem well, that the outline of the solution will basically work should be reasonably self-evident. Many tech talks fail here, because they dive too deep into the details too fast. Again, know your audience, so you know how deep to dive. You can never fit all the details you have in your head into a talk, so think carefully about what the most important features of your solution are, and focus on those. Keep less important details for backup slides you can turn to if asked.<p>The third part is usually evidence that your solution works. Often this involves graphs. Again, focus on only the most important results - more than about three graphs and your audience will switch off. Explain the experiment, and explain what the axes represent. Way too many people don&#x27;t spend enough time on this, so no matter how good the data, no-one understood.<p>Finally, your conclusions. What did you learn? How complete is it? What are its limitations? You&#x27;re not entirely doing a sales job, and your audience are wise enough to know that your system will have limitations. You should be the one to explain them, rather than have them come out in questions (when they&#x27;ll start to doubt eveything else you told them). Finally, what future directions do you think should be taken?<p>Of course, different talks have different shapes. Find what works for you. Sometimes you need to iterate between problem - solution - new problem - revised solution, etc.<p>When you present, know your first few sentences by heart, because you&#x27;ll be nervous. After that, it matters less, you&#x27;ll have settled into the talk, and you&#x27;ll appear less stilted if you&#x27;re not reciting a script. Most importantly, turn your excitement dial to 11. If the audience feel you&#x27;re not excited by the work, why would they be?
khazhoualmost 7 years ago
If you&#x27;re projecting from your own laptop, shut down any apps that might give bouncing notifications. Really, just shut down all apps. And don&#x27;t have your browser open with bookmarks tab and window tabs showing.<p>Don&#x27;t spent 10 minutes on the introduction. A <i>very</i> common mistake is people step too slowly through the setup material. Just lay out the problem and GO. In fact, even throughout the talk, assume the audience is smart and can fill in the obvious blanks.
评论 #17566854 未加载
zwischenzugalmost 7 years ago
Best advice I had about giving talks (from a non-techie) was &#x27;tell a story&#x27;. People like stories more than information. If they want information they can mine you for it afterwards.
评论 #17564700 未加载
评论 #17564490 未加载
dmlorenzettialmost 7 years ago
Try framing your material in the assertion-evidence [0] style. Not only does this lead to more informative presentations, I find it helps me organize my story better.<p>Briefly, rather than using topic titles (&quot;Experimental Setup&quot;, &quot;Results&quot;), use assertions (&quot;Sampling occurred over 5 days&quot;, &quot;Sunlight causes significant degradation&quot;) as titles. Then the bulk of the slide is some information, preferably graphical, that supports the assertion. Reading the titles in order should give you a strong sense of the presentation content.<p>I strongly recommend &quot;The Craft of Scientific Presentations&quot; by Michael Alley, which covers the assertion-evidence approach, and a host of other practical topics.<p>[0] <a href="https:&#x2F;&#x2F;www.assertion-evidence.com" rel="nofollow">https:&#x2F;&#x2F;www.assertion-evidence.com</a>
评论 #17566481 未加载
TamDenholmalmost 7 years ago
If you&#x27;re being recorded for it to go on youtube, and you&#x27;re doing a Q&amp;A at the end, please repeat any questions that are asked for the benefit of the mic and those watching on youtube. Thanks
评论 #17565007 未加载
评论 #17565308 未加载
antirezalmost 7 years ago
Say at least something useful and new that most people in the audience do not know already. If this is not the case, better to rethink the talk from scratch. Audience should go aways thinking &quot;I learned a few new things&quot;.
评论 #17564418 未加载
madethemcryalmost 7 years ago
There are quite some people who are writing full scripts. That&#x27;s also what I prefer. It goes like this:<p>Before creating a single slide, write down sentence by sentence, word by word, what story you want to tell. You can use tools to get a very rough metric of how long your written text will translate being spoken. Stop when you reach your talk length.<p>Once you are done, you can start creating slides. Choose what you like the best and what fits your story. Few slides, many slides (e.g. Pecha Kucha), no slides.<p>I would never do live coding but show small videos instead. I have seen live coding fail more often than being a great success. But if you want to do so, have a fallback video at hands.<p>Now your rehearsal: Not 1 full, not 2 full rehearsals, do as much as you can! For my last and very first talk for a conference I did like 20 full rehearsals, 5 of them in front of people, some in the living room, some in front of the mirror. I bet this can be less in the future but it got me super confident. Rehearsal matters! Don&#x27;t be lazy and you will be amazed how confident you can go into your talk.<p>When you black out during your talk, don&#x27;t panic because you have a full script which you could theoretically read word for word. That always calms me down.<p>Good luck and have fun.
评论 #17565128 未加载
JD557almost 7 years ago
Make sure that your talk fits the timeslot.<p>I find it helpful to go train the whole talk with a metronome (at a slowish tempo) to have an upper bound on how much time the talk will take.
评论 #17564438 未加载
sulsalmost 7 years ago
I came across <a href="https:&#x2F;&#x2F;speaking.io" rel="nofollow">https:&#x2F;&#x2F;speaking.io</a> _after_ I presented for the first time at a larger conference [1]. In hindsight it&#x27;s so obvious -- Zach Holman really talks about the things that matter. So if you still have time, please do your future-self a favour and have a look at it.<p>Another point I found out _after_ I presented is to better avoid any caffeinated drinks -- apparently it makes your mouth dryer. Adding a bit of nervousness makes matters worse and you end up having to drink a sip of water every few minutes.<p>[1] <a href="https:&#x2F;&#x2F;youtu.be&#x2F;wNrTDEaDVwU" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;wNrTDEaDVwU</a>
评论 #17574073 未加载
jedbergalmost 7 years ago
Tell a good story. Humans love stories. Even the most deeply technical talk should have a narrative with a beginning, middle, and end.<p>Start with a bang. Have a controversial opinion? Lead with it. The slide with your name probably shouldn&#x27;t be the first one, unless the conference makes you start that way. This goes back to point one -- telling a good story. You know how most movies start with something really exciting in the first few minutes? This is called the &quot;inciting event&quot; and is what drives the narrative. Your talk should have that too.
joelhooksalmost 7 years ago
The audience wants you to succeed and are generally very forgiving.
评论 #17565123 未加载
krzrakalmost 7 years ago
When rehearsing record yourself (i.e. with your phone mounted on the tripod or just against something). I realized, that before that I didn&#x27;t do full rehearsal, just was repeating the talk in my mind or even if speaking aloud - I was sitting instead of standing, had lots of interruptions, etc. Then watch the recording. It&#x27;s painful, but worth it. Observe your body language. Try to face the audience, not sit or stand with your back towards them to read the slides. Move a little bit, don&#x27;t just stand there.
评论 #17565376 未加载
Scarblacalmost 7 years ago
Plan to give the same talk several times. You can give it to your team, then to some local dev meeting, then on a larger conference. You can improve it over time.<p>Talk clearly, look at your audience, if it&#x27;s hard to hear what you&#x27;re saying at all then there is no point.<p>Make it clear what the problem you&#x27;re solving is, why solving it would be nice, why obvious solutions aren&#x27;t good enough, then work towards a big payoff at the end. Show that your tech solves the problem, and does it very neatly!<p>When explaining stuff, use <i>examples</i>.
jppopealmost 7 years ago
1) Do not attempt to live code. change your code via version control, build small videos, copy and paste... whatever you do... do not try and live code<p>2) Read &quot;The presentation secrets of Steve Jobs&quot; ... its not really about Steve Jobs so much as its about how to be a great presenter.<p>3) building or writing a talk is significantly less important than the delivery... which means that more of your time should be spent on how to deliver the speech (recording I find is the best way to practice)<p>4) Pick a single thing and do it well, do not attempt to put too much into a talk or tackle something massively complex.<p>5) Make sure that everyone is walking away with something they can actually use. This doesn&#x27;t require it be a hard skill... &quot;Soft&quot; or philosophical utilities are just as good<p>6) Have Fun and be funny... Speakers have a tendency to want to show off the size of their intellect, and the level their competency- having a speech be entertaining is way way more important.<p>7) DO NOT READ FROM YOUR SLIDES. know your shit. slides are supplementary<p>Extra Credit. Here&#x27;s a collection of some fantastic technical speeches:<p>* <a href="https:&#x2F;&#x2F;vimeo.com&#x2F;9270320" rel="nofollow">https:&#x2F;&#x2F;vimeo.com&#x2F;9270320</a> * <a href="https:&#x2F;&#x2F;www.destroyallsoftware.com&#x2F;talks&#x2F;wat" rel="nofollow">https:&#x2F;&#x2F;www.destroyallsoftware.com&#x2F;talks&#x2F;wat</a> * <a href="https:&#x2F;&#x2F;youtu.be&#x2F;o_TH-Y78tt4" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;o_TH-Y78tt4</a> * <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=csyL9EC0S0c" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=csyL9EC0S0c</a> * <a href="https:&#x2F;&#x2F;youtu.be&#x2F;a-BOSpxYJ9M" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;a-BOSpxYJ9M</a> * <a href="https:&#x2F;&#x2F;youtu.be&#x2F;kb-m2fasdDY" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;kb-m2fasdDY</a>
eksemplaralmost 7 years ago
As I moved into management I started to give more and more talks&#x2F;presentations. A few very tech talks at summits and conventions with our peers, most were briefings directed at upper management, and while the content are different they function the same really.<p>I start by figuring out what I want my audience to take a way from the talk. Then I break it up in keywords and then I build my presentation.<p>Once that is done I practice once or twice, by my self, talking to the computer while I rearrange, add or delete from the presentation to make it what I want it to be.<p>Once this is done I practice, going through the entire presentation until I’m able to give it on the fly if I was woken up at 4am. I don’t practice it word for word though, but when you’ve talked about a subject enough times, you can do it again.<p>The practice but is really, really important. Especially if you’re not used to giving speeches. At first I thought that if I just practiced in my head, I’d be fine, because I knew what I wanted to say. Hah, not so. The first time I gave a presentation I was a stuttering incoherent mess, because I hadn’t practiced by saying the words out loud. I knew exactly what I wanted to say, I just couldn’t.<p>Now, many years later, I don’t have to practice as much because I’ve gotten better verbally. So yo can definitely be the type of person who doesn’t need to practice out loud. But I had to do more than a thousand presentations to get to a point where I could comfortably skip practicing on short presentations and only doing it once or twice on long ones.<p>As for questions afterwards, take your time to think about your answer, and if you don’t know the answer, then be honest and always, always be polite and affirmative. If you make people feel like they asked a good question, even when you think it wasn’t, then they and everyone around them will like you better. This too gets better with practice, but it’s obviously not something you can practice on your own.<p>Humor is typically a good thing, it relies a lot in timing and it sometimes falls flat. Just never do it at someone’s expense.
tchaffeealmost 7 years ago
If your slide has writting on it, people will read your slide instead of listening to you. Keep the writing to a bare minimum and fill in the missing parts. Even better, use a picture that helps tell your story for that slide.<p>For each slide, think about what the audience take-away is. They should learn something from what you say for each slide.<p>Mingle and introduce yourself to a few people before your talk but don&#x27;t tell them you are a speaker. Before you get on stage see if you can find them in the audience and pretend you are talking to them and not a huge audience. If you can&#x27;t find some known faces, pick one from the first few rows. Helps with the nerves.<p>Until you get good at speaking, you need a lot of rehearsal for each talk. Present once in front of a willing friend and then after making corrections, get a few volunteers at work to be an audience. As many rehearsals as possible.<p>Slow down. Pause. People need a little time to digest each idea. Your material is new to them.<p>Like everything in life, the only way to become good is to make mistakes. With speaking you do that in front of a lot of people. It helps if you can laugh at yourself and be forgiving. The audience will often treat you the way you treat yourself.
评论 #17569341 未加载
mindcrimealmost 7 years ago
My biggest suggestion is this:<p>1. Don&#x27;t read the slides to your audience. Generally speaking, the audience can read.<p>So what are slides for then? Well, if it&#x27;s a text only slide, I treat them as being there to be <i>reminders of what I&#x27;m supposed to talk about now</i>. And that&#x27;s it. The content is what I say, not what&#x27;s on the slide. So there doesn&#x27;t actually need to be much on the slide at all. Just a couple of bullets to reflect the high points of the conversation. Now graphics are a different story.<p>There are exceptions, of course. I&#x27;ve been known to do a slide with a massive list of &quot;things&quot; in 10 point font, with like 30 items on it... but when I do that, it&#x27;s to <i>make a point</i> - a point like &quot;there are a fuck-ton of options for X&quot; or whatever.<p>The other thing I try to do, is put links and pointers to other resources somewhere in the deck, so that sharing it with the audience actually provides some value. If you adopt the &quot;very information sparse&quot; slide format, then the slides don&#x27;t really provide much value to the audience after the fact. Whether that&#x27;s an issue or not is kinda up to you.
koolbaalmost 7 years ago
Finish your slides <i>at least</i> a few weeks before the talk and dedicate a time slot equivalent to the talk (ex: 1-hour =&gt; 1-hour, 30-min =&gt; 30-min) per week doing a dry run. This is particularly important to get the timing correct. If you&#x27;re repeatedly short or long then adjust accordingly.<p>Version control your slides. This is particularly useful if you end up giving the same talk more than once as you can tweak things and improve it.<p>It&#x27;s a tech talk, not a stand-up comedy routine. Light jokes and colorful anecdotes help with connecting to the content but the substance should stand on it&#x27;s own.<p>Depending on your alcohol tolerance 1-2 drinks can be remarkably effective at smoothing out your delivery.<p>I find a small intro on the format of the presentation to be helpful at setting expectations. The talk descriptions are often very short and it&#x27;s hard to gauge what&#x27;s actually going to be covered with a lot of &quot;<i>Deep dive into XYZ</i>&quot; barely getting your ankles wet with real code. It&#x27;s appreciated (as an audience member) to know in advance what you&#x27;ll be getting.
评论 #17566791 未加载
3stadtalmost 7 years ago
In my experience, one of the most important things is to keep your audience in mind. I recently gave a talk about how docker works internally. I knew that a good chunk of the audience was aware of the difference between docker and a VM, so in the beginning, I explained these differences via a more or less fun story. People who already knew the content were not annoyed, the rest got the information they needed.<p>Another thing is, tech talks tend to be as dry as the Sahara desert. So try to make your talk interesting. Do not just focus on getting the information across, but make it fun to listen.<p>Practice your talk without slides. This has two benefits: You concentrate on the content, so your stuff by heart at the end. And you don&#x27;t depend on the slides, in case something goes wrong.<p>Lastly, prepare for 4:3 - even if they say you get a 16:9 beamer, chances are it&#x27;s not. And prepare for offline, your Laptop being broken and in case you are doing a live demo: Have a video of it as a backup.<p>These tips are all just from my experience and may not apply to you, but maybe it&#x27;s helpful. :)
评论 #17564865 未加载
评论 #17570817 未加载
erichurkmanalmost 7 years ago
Do not assume everyone knows acronyms or initialisms that you use, particularly if the audience is unknown. Saying &quot;test driven development&quot; is more accessible to a wider audience than &quot;TDD&quot;.
评论 #17565957 未加载
nicostouchalmost 7 years ago
If there is a Q&amp;A section and it&#x27;s being recorded... please please please repeat the question so your mic pics it up because the person asking it is miles away and it never makes it into the audio so the people watching at home later have to guess what the question is based off the answer you gave which can be tough sometimes. So just a &quot;Ok, so the question is... blah blah blah - answer&quot;.<p>Also... nothing can quite prepare you for how shot your nerves can be. It definitely pays to run it through many times as you can with a timer so that you are at least confident in your pacing.<p>Other than that it&#x27;s quite fun.<p>It can be pretty handy to you to include your twitter handle in the top right corner so you get some follows throughout the presentation from people who were interested. At the end link off to &#x27;you can find the slides for this presentation here bit.ly&#x2F;soloyolo&#x27; etc.
LawnDart1almost 7 years ago
Understand your audience.<p>It&#x27;s SO easy to assume knowledge. When I talk about python, I now give a quick intro to the command prompt. I started out assuming everyone knew how to use the command prompt. A lot of times, you forget that the stuff you &quot;just use&quot; may be new to the listeners.
vpribishalmost 7 years ago
who is your audience? where are they starting from? know this before going in.<p>get there very early and check that the tech is sorted.<p>have a short list of explicit goals - feel free to write them out.<p>practice at least once, for real, out loud. If no one will help, present the talk to a stuffed bear.<p>do not read your slides to the audience.<p>expect live demos to fail - have a practiced contingency plan.<p>no lewd illustrations and don&#x27;t put people down - you are in a position of responsibility.<p>at the end, sum up.
petecooperalmost 7 years ago
Former tech trainer and presenter here. In no particular order:<p>* start by telling everyone what you&#x27;re going to tell them, then tell them, then tell them what you just told them;<p>* know your material well enough that when your computer stops working you can carry on seamlessly;<p>* rehearse in front of a mirror or record and watch yourself;<p>* if you&#x27;re talking too quickly, take a quiet breath and make sure you pronounce the last letter of each word that you speak;<p>* switch your slide to black or white when you&#x27;re making a very important point, and have them focus on you instead of the screen -- use `b` key for black and `w` key for white, works with most presentational software I&#x27;ve used;<p>* …and smile
kashyapcalmost 7 years ago
How do you prepare and how <i>long</i> do you ought to spend preparing the talk? I&#x27;ll quote `techtalk-pse`[1][2]:<p>[quote]<p>First, most important rule: Before you start drawing any slides at all, write your talk as a short essay.<p>This is the number one mistake that presenters make, and it is partly a tool fault, because PowerPoint, OpenOffice, even Tech Talk PSE, all open up on an initial blank slide, inviting you to write a title and some bullet points. If you start that way, you will end up using the program as a kind of clumsy outlining tool, and then reading that outline to your audience. That&#x27;s boring and a waste of time for you and your audience. (It would be quicker for them just to download the talk and read it at home).<p>A good talk, with a sound essay behind it, well thought out diagrams and figures, and interesting demonstrations, takes many hours to prepare. How many hours? I would suggest thinking about how many hours of effort your audience are putting in. Even just 20 people sitting there for half an hour is 10 man-hours of attention, and that is a very small talk, and doesn&#x27;t include all the extra time and hassle that it took to get them all in one place.<p>[&#x2F;quote]<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Tech_Talk_PSE" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Tech_Talk_PSE</a><p>[2] <a href="http:&#x2F;&#x2F;git.annexia.org&#x2F;?p=techtalk-pse.git;a=blob;f=techtalk-pse.pl;h=b49591;hb=HEAD#l869" rel="nofollow">http:&#x2F;&#x2F;git.annexia.org&#x2F;?p=techtalk-pse.git;a=blob;f=techtalk...</a>
EnderMBalmost 7 years ago
The best advice I can give to you is that if you&#x27;re giving a talk on something that you&#x27;re not an expert on, then tell people you&#x27;re not an expert.<p>I gave a talk a year ago about Continuous Delivery, despite being a bog-standard developer that has had to do it on a couple of occasions. I had some general rules that I could carry across from one company to another, so my talk was around these general paths to happiness, and discussing the tools I have used, alongside a generous Q&amp;A.<p>The questions were all fairly straightforward, and a number of people came up to me at the end to share the same sentiments - they were developers that had been roped into doing sysadmin stuff, and that they found the talk and answers to be very useful.<p>I have a theory that people often go to talks not to learn something new from an expert on the subject, but for a structured developer chat around an approach on a subject that seems to work for someone in a given context. If they&#x27;ve attended, they&#x27;re interested in the subject, so as long as what you say is on-subject and clear it&#x27;s difficult to give a bad talk. From there, it&#x27;s mostly around delivery, which comes with practice and preparation.
gradschoolalmost 7 years ago
The first few minutes are when the audience is most attentive, so don&#x27;t waste it but jump right in with a motivating example or whatever is the most interesting thing about your talk. Then when you have them on the hook you can give them the outline and overview for the rest of the presentation as usual. I got this advice from a presentation given by Simon Peyton-Jones and have always tried to follow it since then.
bryanrasmussenalmost 7 years ago
What do you do when the demo fails. I like to get all flustered and go down in flames but you might prefer to have a way of dealing with that eventuality.
radford-nealalmost 7 years ago
Have something to say. Something that you WANT to say. If you don&#x27;t have that, cancel the talk.<p>So you want to say something. Say it.<p>Don&#x27;t start your 20 minute talk by spending two minutes going over an outline of it, saying that you&#x27;ll first present the problem, then review past work, then blah, blah, blah. I HOPE that the thing you want to say isn&#x27;t &quot;I&#x27;ve spent a lot of time organizing my talk like this...&quot;<p>Don&#x27;t start your talk with a funny anecdote about the driver of the taxi you took from the airport. I hope that THAT isn&#x27;t what you want to talk about either.<p>Do start by describing the problem you&#x27;re solving (you are solving some sort of problem, I assume...?). But only to the point where the audience can grasp what you&#x27;re trying to do. Review past work only if the focus of your work is something like &quot;I fixed the problem that the XYZ algorithm unnecessarily recomputes A...&quot;. You can mention how past work relates to yours at the end of the talk. It will make more sense then.<p>Get as quickly as you can to WHAT YOU ACTUALLY ACCOMPLISHED. I hope that&#x27;s what you want to talk about.
ThorinJacobsalmost 7 years ago
The number one thing I love to see when I&#x27;m watching a tech talk that is focused on teaching or advertising a particular tech is the Bad Parts. Obviously you don&#x27;t want to just bash the tech you&#x27;re there for, but I&#x27;ve seen way too many demos that portray the technology as the One True Technology that will Solve All Your Problems and I usually approach tech talks from a place of skepticism.<p>Alice Goldfuss&#x27; recent talk on containers[1] is a really good example of what I&#x27;m talking about - she spends a good amount of time talking about what containers are, and why and when it would appropriate to use them, but she spends an equal or greater amount of time preparing the audience for what challenges they will encounter when implementing containers and talks about when you&#x27;re probably better off without.<p>[1] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=sJx_emIiABk" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=sJx_emIiABk</a>
larquinalmost 7 years ago
Never assume that your audience knows anything of real substance about your talk. You&#x27;ve spent many hours building up knowledge and context about the subject, and your audience is coming in cold. I&#x27;ve rarely been to a talk where the speaker &quot;over explained&quot; the material.
meukalmost 7 years ago
Make the objective of your talk clear. If you&#x27;re giving an introduction to some technology, it is helpful to also point people to resources to learn more. If you need to explain or &#x27;sell&#x27; your topic, do so, but don&#x27;t overdo it. Also, be honest. Everyone appreciates enthusiasm, but it&#x27;s better if you don&#x27;t come across as a fanboy.<p>If you&#x27;re having an interactive part, be aware that it is hard to estimate the time this part will take. If you have a hard deadline, be ready to skip some parts (this is a good idea in general as things may always<p>It&#x27;s probably best if you are so familiar with the topic that you don&#x27;t really need slides in the first place. On the other hand, take care to connect with your audience and take their background into consideration.
pacohopealmost 7 years ago
Stick to the topic, and don&#x27;t go meta. Leave out things like &quot;when I was preparing to submit this talk proposal&quot; or &quot;as I was creating the slides for this talk.&quot; Talk about the topic, don&#x27;t talk about the talking.<p>Know the language and culture of your audience. If it&#x27;s a mixture of people who don&#x27;t speak English (or whatever language) as their first language, take care to avoid colourful metaphors that make sense to a native speaker but which confuse non-native speakers. I&#x27;ve confused people with expressions like &quot;inside baseball&quot; or reference to &quot;Goldilocks values&quot; (not too much, not too little). Good metaphors are valuable. Metaphors that depend on too much cultural context are unhelpful.
mohitmunalmost 7 years ago
<a href="https:&#x2F;&#x2F;www.deconstructconf.com&#x2F;blog&#x2F;how-to-prepare-a-talk" rel="nofollow">https:&#x2F;&#x2F;www.deconstructconf.com&#x2F;blog&#x2F;how-to-prepare-a-talk</a> This is really good write up on similar topic by Gary Bernhardt.
viraptoralmost 7 years ago
Something practical I haven&#x27;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&#x27;s hanging low (so most people can&#x27;t see the bottom of the slides).
评论 #17565004 未加载
darekkayalmost 7 years ago
There is a lot of good content advice here. I&#x27;d like to add two technical points:<p>- Plan for the worst-case scenario, e.g. your computer dying. All my presentations are available on GitHub Pages[0] (using RevealJS), so all I need is a random laptop.<p>- Use a bright color theme on a beamer to improve readability (slides, console, editor&#x2F;IDE). Dark schemes are nice, but they are inappropriate for most presentations. Bonus: when using HTML slides, you can design both a bright and dark theme and switch depending on the light conditions.<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;darekkay&#x2F;presentations&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;darekkay&#x2F;presentations&#x2F;</a>
TH3R3LL1Kalmost 7 years ago
I&#x27;m a Toastmasters member, and one of the things I learned with presenting technical talks is that you should know your audience. If your audience understands the tech, then speak at a technical level, otherwise speak at a very high level
bastijnalmost 7 years ago
- Don&#x27;t put too much on your slides.<p>- Don&#x27;t put too much on your slides.<p>- Don&#x27;t put too much on your slides<p>See if you can do without any bullet list. Now you are forced to talk from your experience in a natural form. You&#x27;ll be fine.<p>More serious:<p>- don&#x27;t go into the trap of too much introduction and theory before getting to the actual matter. E.g. when doing a talk on GPU image processing don&#x27;t spend 30 minutes on how a GPU works.<p>- Know your audience experience with the matter if possible (see above)<p>- If possible, do demos. If have demos, consider if it makes sense to run them _before_ the tech slides. They tend to make more sense after seeing a live demo.<p>- If you have demos, rehearse them. Make sure you get the timing right.<p>- leave room for questions.
bborehamalmost 7 years ago
Introduce yourself.<p>Way too many times I’m sitting in the audience, the person at the front is exchanging smiles with the programme committee who all know each other, but I have no idea who they are and what drives their viewpoint.
oferzeligalmost 7 years ago
<a href="https:&#x2F;&#x2F;www.hanselman.com&#x2F;blog&#x2F;11TopTipsForASuccessfulTechnicalPresentation.aspx" rel="nofollow">https:&#x2F;&#x2F;www.hanselman.com&#x2F;blog&#x2F;11TopTipsForASuccessfulTechni...</a>
ioddlyalmost 7 years ago
If you&#x27;re showing code, use way less code than you initially want to.
LoSboccaccalmost 7 years ago
Chances are you’re an expert in the field! Great! Rember not everyone in the audience is.<p>Keep in mind who you’re talking to and what they’ll bring home from your talk.<p>Will they use it on their job? Then it’ll need operational details. It’s just something cool you did? Make sure it’s a good story with villains (problems) henchmen (bugs) and it stays relatable all the way to the victory. Is somerhing that pushes the envelope of what’s known? Make sure to establish the state of the art and guide the audience through the wonder of the discovery process.
eb0laalmost 7 years ago
Don&#x27;t start with powerpoint. Get pen and paper. DRAW what you want to tell. If the result is good you can scan that drawing to make a slide.<p>This way I don&#x27;t overspend time on tools, but on content.<p>Hope this helps
carusoonelineralmost 7 years ago
Simple things that have helped me:<p>- Right before the talk: get to the room well ahead of time and make sure there are no setup issues with the laptop, audio, projector, etc. I&#x27;ve seen a number of speakers fail to do this basic thing and it dampens their flow, confidence, etc. The audience might even get distracted and the whole show goes awry.<p>- Prepare and practice the intro speech, don&#x27;t wing it: if you have a good opening, you&#x27;ll feel confident and the momentum will carry you through the rest of the talk.
vfulco2almost 7 years ago
Don&#x27;t do a Ubuntu update the day of the speech. I did then closed my laptop, headed to the venue to give a 30 minute workshop on best practices in resumes and the reasons for a LinkedIn Profile in front of 40 people, and bootloader was corrupted. Thankfully I had backup of folder (reveal.js presentation written with rmarkdown) on USB. I usually zip up and email a copy to the organizer, just in case.
alexcnwyalmost 7 years ago
Casually give an informal version of the talk to some friends or colleagues to see if they &quot;get it&quot;.<p>I find that talking it through a few times with someone will help you figure out which parts of your explanation are unclear and need rephrasing.<p>Also, don&#x27;t take it too seriously - technical talks are already often dry - don&#x27;t be afraid to insert some memes and jokes to keep the audience engaged!
lbrineralmost 7 years ago
Don&#x27;t try and cover too much ground in the time - it is generally quicker than you think. Have a strong story arc however so that any questions can be asked at the end during the presentation or afterwards.<p>You can always put slides and examples online and refer to them, especially if in another country where people might not keep up with your native language.<p>Smile a lot!
jackthetabalmost 7 years ago
Two things I haven&#x27;t seen ITT yet:<p>1. After you tell me what you&#x27;re going to talk about, tell me why I should be listening to _you_. Why are you an authority on this topic? Unless you&#x27;re famous, I don&#x27;t know you.<p>2. The talk should contain 50% or less of your knowledge on the topic. You want to keep some info &quot;in your back pocket&quot; to ad lib with.
评论 #17570262 未加载
corysamaalmost 7 years ago
I frequently see speakers end their talk with “Any questions? No questions?? I was really perfectly clear? OK. Bye!” That fast.<p>It takes at least ten seconds for people to formulate a question well enough to ask it in front of everybody. Have some patience. Bonus points for having something low-key to fill the awkward silence.
rjrodgeralmost 7 years ago
I write a weekly newsletter on this exact topic - you might find it useful :)<p><a href="http:&#x2F;&#x2F;blog.voxgig.com&#x2F;2018&#x2F;07&#x2F;13&#x2F;welcome-voxgig-newsletter-event-speakers-july-13th-2018&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.voxgig.com&#x2F;2018&#x2F;07&#x2F;13&#x2F;welcome-voxgig-newsletter-...</a>
wilaalmost 7 years ago
I had filed this one (1) away for next time I have to do a presentation. It sums up a list of bad titles for a presentation.<p>[1] <a href="https:&#x2F;&#x2F;gist.github.com&#x2F;snare&#x2F;7f0c4708bf4ea8133204c21e8ba64d23" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;snare&#x2F;7f0c4708bf4ea8133204c21e8ba64d...</a>
edsiper2almost 7 years ago
in my experience I would consider the following:<p>- Understand what are your takeaways for the audience. Remember it&#x27;s about the content, keep in mind main areas&#x2F;topics to cover.<p>- who&#x27;s your audience ?, there are a few conferences where going very technical (low level) matters, most of them want to focus on how X works, how to solve Y, etc.<p>- &quot;Start with why&quot;. Yeah, it should sound familiar, check this 5 minutes video: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=IPYeCltXpxw" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=IPYeCltXpxw</a> .<p>- Note that likely in the first 3-5 minutes the audience will have a &gt; 90% focus on what are you talking about, make sure to take advantage of that time with a good &quot;why&quot; (see above) for engagement.<p>- Share your presentation slides with a colleague and wait for &quot;honest&quot; feedback.
gauravguptaalmost 7 years ago
Here&#x27;s a blogpost I wrote on dos&#x2F;donts of giving tech talks - <a href="https:&#x2F;&#x2F;medium.com&#x2F;@gauravgupta&#x2F;make-a-powerful-point-the-next-time-you-present-d77f60e92fec" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;@gauravgupta&#x2F;make-a-powerful-point-the-ne...</a>
mrestkoalmost 7 years ago
No matter how small the room is, or how much you think you can project, use the microphone. I can&#x27;t stand when people say, &quot;I have a loud voice, I&#x27;m not gonna use the microphone.&quot; And then either scream for an hour, or fade in and out of intelligibility.
crocalalmost 7 years ago
- What is your message? You do this talk for a reason, it must be extremely clear to you what it is, in a short sentence or two.<p>- Storytelling. Humans engage in stories. Prepare yours.<p>- Rehearse. Rehearse. Rehearse. And when you are done, rehearse again fixing everything that was not perfect.
yagyualmost 7 years ago
TLDR; Recognize impostor syndrome and include &#x27;basics&#x27; even in presentations for highly skilled people.<p>I&#x27;m in the physical sciences and routinely give fairly math-heavy presentations.<p>It&#x27;s easy to think that an audience of Phd&#x27;s and professors know all prerequisites and just need the hard facts in a rapid succession.<p>On the contrary over time I found that my audience typically appreciates when I start from the very beginning (in my case meaning advanced undergraduate level or so), and working up to the actual problem setting.<p>Although my audience is very much expected to know that material they A) get primed for the topic and have a chance to feel good about &#x27;I know this&#x27; and B) understand my view of the topic so that we have a common language.<p>With that I&#x27;m ready to frame the technical problem and explain my work.<p>The last time I did this I actually spent 10 out of 20 minutes on the first part, and the talk was very well received and generated an &#x27;invited paper&#x27; request for a journal.<p>No one has ever complained that my talks are &#x27;too basic&#x27;.<p>EDIT: Btw, the metric I use to measure success is amount of generated questions &amp; engagements in and after the talk. If the moderator has to cut off Q&amp;A for the next speaker you win. If people hunt you down to talk more you win.
nomadiccoderalmost 7 years ago
The why is much more important than the how. The job of the talk is to convince people to read your paper. Focus on motivating your work, overview how the approach was done and the results but the setting for the problem is much more important.
eldavidoalmost 7 years ago
Keep the needs of the audience in mind.<p>More: <a href="http:&#x2F;&#x2F;www.davidralbrecht.com&#x2F;notes&#x2F;tags&#x2F;engcomm.html" rel="nofollow">http:&#x2F;&#x2F;www.davidralbrecht.com&#x2F;notes&#x2F;tags&#x2F;engcomm.html</a>
linker3000almost 7 years ago
Plan for any tech or other collateral to not work properly on the day and have contingencies to continue - even things such as having a printout of your presentation storyboard or bullet points to hand.
qaqalmost 7 years ago
I will sound like an @$$ but get to the point quickly so many times 1 hour talk could actually be condensed to like 5 minutes of actual information. I wish there was a service that actually did this :)
yulealmost 7 years ago
Kelsey Hightower had some insightful tips in this recent podcast: <a href="http:&#x2F;&#x2F;testandcode.com&#x2F;43-bonus" rel="nofollow">http:&#x2F;&#x2F;testandcode.com&#x2F;43-bonus</a>
cafardalmost 7 years ago
Have a look at <a href="https:&#x2F;&#x2F;perl.plover.com&#x2F;yak&#x2F;presentation&#x2F;" rel="nofollow">https:&#x2F;&#x2F;perl.plover.com&#x2F;yak&#x2F;presentation&#x2F;</a>
amorphousalmost 7 years ago
- Rehearse in front of a friend.<p>- Add as little text to your slides as you can<p>- Accept that you will get nervous. We all do, being nervous is not a problem, the fear of it is.<p>- Remember, the audience wants you to succeed
ValleyOfTheMtnsalmost 7 years ago
Who are your audience? What is their level of knowledge? What do they want to know? What DON&#x27;T they want to know? Why should they care what you&#x27;ve got to say?
madhadronalmost 7 years ago
I&#x27;ll give you what I do. I assume that tech talk here means seminar and not class. For a class I do things differently. First, write down the goal of the talk. What should the audience know, be able to do, etc. after this talk? If it&#x27;s more than three bullet points, it&#x27;s time to start cutting. Remember, in a talk, everyone is at the mercy of your pacing. Any given audience member will probably space out for at least five minutes of an hour talk, and if you&#x27;re at a conference or embedded in a workday, they&#x27;re already overwhelmed with information.<p>Then sketch an outline of presenting that information, just a rough order of what to touch on. I find that I naturally outline so that each entry is about five minutes, but I don&#x27;t know if that&#x27;s just me or a common tendency.<p>Then I get a timer, stand up, and start talking to myself. I&#x27;ll take an outline entry, and try to tell an imaginary audience about it. Typically I realize that I have some questions I need to answer for myself, or I run over five minutes. Think about how to drop stuff, look up what you need, note down what bits of verbiage came out that flowed well to reinforce them for yourself, and do it again. I often get frustrated after two or three times on one item, and go do another one, then come back to it and do it some more. During this whole process pretend the perfect slide to go with your text is up next to you so you can point.<p>After some cycles, this will converge. You will know what you want to say, and you will know what needs to be on the slides. Now set the timer for the full talk length and give the whole talk like this, still with pretend slides. You&#x27;ll probably find places where you need transitional material, and it will probably run long despite the fact that the pieces add up to fit. Adjust. Do it again. This is also a good time to figure out and memorize the first couple sentences of each section, which will let you transition easily if you lose your place.<p>At this point you know your talk. Now go sketch your slides out on paper, and give your talk pointing to the paper. Once you think you have what you need figured out on paper, then go turn them into a PowerPoint, PDF, whatever.<p>Now practice it with the slides. Practice starting from a section using those memorized sentences. Memorize your sequence of outline items with those sentences attached.<p>Then do a run-through the day before. The day of, I spend five minutes thinking through my outline and section starting sentences, take a deep breath, and talk as inhumanly slow as you can. Even if you don&#x27;t have stage fright (I don&#x27;t), you will have adrenaline, and you need to slow down.
ed_at_workalmost 7 years ago
You probably know more about the subject than the people you are speaking to. So, when appropriate, err on the side of giving more background info than less.
pgreenwoodalmost 7 years ago
1. Describe the problem you&#x27;re trying to solve.<p>2. Describe your approach to solving it.<p>In general, have something to say, know your stuff, and the rest will flow naturally.
samlittlewoodalmost 7 years ago
When practicing and figuring timing, I find it helps to do it out loud. I go way too fast if I don’t properly vocalise it.
sidcoolalmost 7 years ago
I find code in slides a bit distracting. It&#x27;s better to have code in a separate editor (which can be run too!).
caymanjimalmost 7 years ago
Proofread everything you plan to display, because spelling and grammar errors can negate your authority (hint ^^^).
geronimo404almost 7 years ago
can keep in mind transitions between slides, whether working your way through the current slide as intended or digressing. these transitions can contain a purpose for arriving at the end of the current slide + relevance to the upcoming ones
hazboalmost 7 years ago
These are some things that I generally keep in mind whilst preparing or giving a talk. (These are just things I do, feel free to disagree.)<p>Preparing: 1) Give yourself enough time to write and practice the talk. If you can get ~1 month, that (for me atleast) is more than enough time.<p>2) Say the words out loud when practicing. You may use different words or slightly improvise during the talk, which is totally fine. Just let yourself hear some version of it a few times (out loud) before presenting. In my experience this helps to avoid stutters, and keeps you in your place.<p>3) Watch talks of people online that you enjoy or by people that inspire you. We all have our own &quot;style&quot; when it comes to public speaking. You will never be able to straight up copy someone. But watch and take mental notes as you do.<p>4) (If you are preparing slides), keep them simple! It is YOU who is presenting the talk. Not a wall with a projector. Treat your slides mostly as an accessory. They can help illustrate a point perhaps, or outline the key subjects. Short and simple.<p>Presenting: 1) If you can, make sure you have a bottle of water handy when you go up.<p>2) When I approach the stand, platform or stage, I like to do so with confidence. This really does depend on the setting. But for example, as I walk up, sometimes I&#x27;ll take my jacket off. Or do something that otherwise makes me feel like I&#x27;m owning the space. This makes me feel much more comfortable and puts me off to a good start. Even if you&#x27;re not a confident person, walk up as if you are or do something simply to make you feel more comfortable.<p>3) Don&#x27;t be afraid to use the space you have been given. This goes both for actually walking around, and using your arms to assist your words. Hands out of pockets. Use them.<p>4) Pauses are a good thing! Whether it&#x27;s just to take a sip of water, or just a pause for the sake of pausing. This both gives you a few moments to collect your thoughts and also a few moments for the audience to digest what you have just been saying.<p>5) Slowww it down. It&#x27;s almost too easy sometimes to rush talks when it comes down to actually presenting one. Take your time. They came to see you! So make it worth their while.<p>6) This is slightly tricky in some cases, but try to calibrate yourself towards the audience. For example, in my case, I&#x27;ve found people seem to pay more attention if I&#x27;ve just said something slightly amusing. If you can get away with it, go for it! It&#x27;s a hard one to explain, but the bottom line is, try to get the crowd on the same page. I&#x27;ll perhaps think of a better way of explaining this one and reply to this comment.
BenFrantzDalealmost 7 years ago
Ask yourself: “Who is my audience?” Everything else comes from that.
sowbugalmost 7 years ago
If you get butterflies or a racing heart, take three deep breaths.
kevlar1818almost 7 years ago
As a tech conference audience member, one of my biggest pet peeves is people using roughly 70+ percent of their talk to introduce the background&#x2F;rationale of their tool&#x2F;library&#x2F;use-case&#x2F;workflow&#x2F;whatnot without even showing precisely what the tool does or how to use it practically. Chances are, most people in the audience are in the room _because they are already on board with your rationale_.<p>A fake example: If you&#x27;re giving a talk on your new Linux shell that &#x27;s way better than Bash, you don&#x27;t need to spend the first two-thirds of your talk explaining what Bash is and what its weaknesses are. Your audience probably knows what Bash is and knows enough to be interested in an alternative. Don&#x27;t bore them out of the room.<p>TL;DR: Show first, tell second.
jimothyhalpert7almost 7 years ago
Proofread the title. Pay attention to articles...
jkaaynalmost 7 years ago
One thing that has always helped me is mugging the first few lines until you can get in your rhythm. Sometimes that glare of hundred eyes causes you to forgot about your talk.
评论 #17564457 未加载
growlistalmost 7 years ago
A technique that works really well for me is to focus hard on the fact that my job is to be merely a conduit for information, and any anxiety I might feel is just another factor that might impact my ability to convey that information. My feelings then become secondary because my whole focus is on the message. Sometimes I still get an adrenaline rush at the start, but this dissipates as I focus on the content. Other times I am completely relaxed throughout.