国际大会演讲ppt_如何在会议或活动中接受技术演讲

国际大会演讲ppt

by Amanda Sopkin

通过阿曼达·索普金(Amanda Sopkin)

如何在会议或活动中接受技术演讲 (How to Get a Technical Talk Accepted at a Conference or Event)

So you have been considering getting into the conference speaking field? Well you’re in luck, it’s a great time to jump in! Maybe you gave a talk at a local meetup and enjoyed it. Maybe you attended an event recently and started to think about ways you could contribute to the attendees. Maybe you ran across a good talk on YouTube that inspired you.

所以您一直在考虑进入会议演讲领域？ 好吧，您真幸运，这是个加入的好时机！ 也许您在当地的聚会上发表了演讲并很享受。 也许您最近参加了一个活动，并开始考虑可以为参加者做出贡献的方式。 也许您在YouTube上遇到了一个很好的演讲，启发了您。

I have been speaking at conferences, reviewing proposals for events, and coaching new speakers for the last couple of years. I find that many people have misconceptions on the subject, like “I need tons of experience before I can speak at an event” or “speaking at events is invite only”.

在过去的几年中，我一直在会议上发言，审查活动建议并为新演讲者提供辅导。 我发现许多人对此主题有误解，例如“在活动发表之前我需要大量的经验”或“在活动中发表演讲仅受邀”。

But there is a growing movement in tech to make speaking more friendly to beginners and more welcoming as a whole. More and more events even have a separate application (call for proposals) process for beginners.

但是，越来越多的技术运动使演讲对初学者更加友好，并且整体上更受欢迎。 越来越多的事件甚至为初学者提供了单独的申请(征集建议)流程。

选择一个主题 (Picking a Topic)

The process of coming up with ideas for your next proposal can be more similar to that of songwriting than something more systematic, like approaching a technical problem. Inspiration comes from many different places and in many different forms. Here are some ways that I have come up with talk ideas:

提出下一个建议的想法的过程可能与歌曲创作的过程更相似，而不是像解决技术问题那样更系统的过程。 灵感来自许多不同的地方，形式多种多样。 以下是我提出谈话创意的一些方法：

• I saw a talk with X format and decided to apply it to Y subject.
  我看到了一个X格式的演讲，并决定将其应用于Y主题。
• While working on a project, I thought, “Wow! I wish I knew X, Y, and Z before I started!”
  在进行项目时，我想：“哇！ 我希望我在开始之前就知道X，Y和Z！”
• A conversation with coworkers about X led me to see the potential for a talk on it.
  与同事进行的有关X的交谈使我看到了进行此讨论的潜力。

With these approaches I start out with the idea and then find a way to make it work for the conference. For example, when I applied to speak at Pycon I knew I wanted to talk about computational randomness. So I started there and then added to the Python specific meat of the talk. You can also start with the conference in mind and brainstorm ideas from there. By using this method, my thought process was more like:

通过这些方法，我首先提出了这个想法，然后找到了使之适用于会议的方法。 例如，当我申请在Pycon演讲时，我知道我想谈论计算随机性。 因此，我从这里开始，然后将其添加到特定于Python的讨论中。 您也可以从会议开始，然后从那里进行头脑风暴。 通过使用这种方法，我的思维过程更像是：

• These are the top X, Y, Z ideas people are looking at in this language/framework now.
  这些是人们现在正在以这种语言/框架查看的最重要的X，Y，Z想法。
• This conference tends to have talks in X and Y subject areas every year.
  该会议倾向于每年在X和Y主题领域进行演讲。
• An event is specifically requesting talks in Z field.
  一个事件专门要求在Z字段中进行对话。

Personally, I have found the first approach to be more successful. Often, starting with the conference in mind can lead you to write talks that you think the conference wants, rather than writing something you are genuinely passionate about. Also, people tend to come up with similar ideas which can put you in a bigger pool of competition (i.e. writing 1 of the 100 talks about the basics of machine learning in Python vs. a unique problem you are particularly suited to solve).

就个人而言，我发现第一种方法更为成功。 通常情况下，在考虑到会议开始可能会导致你，你认为会议希望，而不是写一些你真正充满热情写会谈。 同样，人们倾向于提出类似的想法，这可能会使您参与到更大的竞争中(例如，撰写100篇关于Python机器学习基础知识的演讲之一，以及您特别适合解决的独特问题)。

写你的摘要 (Writing your Abstract)

Once you have the idea, it is time to jump into representing it in the best light possible. One of the biggest misconceptions in conference submissions is that you don’t need too much effort into this step because

一旦有了想法，就该以最好的视角来代表它了。 会议提交中最大的误解之一是您无需为此付出太多努力，因为

A. You are too important or

答：您太重要了，或者

B. Your idea speaks for itself.

B.您的想法不言而喻。

Unless you have been specifically invited to speak (at which point you can decide your own topic with some input from the organizing team), your proposal will often go through a blind review process where it has to fend for itself against the other (well-written) proposals.

除非特别邀请您发言(此时，您可以根据组织团队的意见来决定自己的主题)，否则您的提案通常会经过盲目审查过程，因此必须与其他提案抗衡(好吧，书面)提案。

And details are important! Reviewers are busy people often reading hundreds of proposals for an event. If there is not enough content there, they will not guess what you could have meant. They will mark it down and move on - regardless of your qualifications.

细节很重要！ 审阅者很忙，经常阅读数百项有关活动的建议。 如果那里没有足够的内容，他们将不会猜到您的意思。 无论您的资历如何，他们都会将其标记并继续前进。

With the importance of this writing stage in mind, here’s a little about my process once I’ve got an idea…

考虑到这个写作阶段的重要性，这里有一些关于我的想法的想法……

首先写描述 (Write the description first)

Conferences have varying requirements for a submission, but I often start with a more detailed description and outline to solidify my ideas as recommended by Alaina Kafkes in this piece. This helps me illuminate the most important stuff that I want to talk about.

会议对提交的要求有不同的要求，但是我经常从更详细的描述和大纲开始，以巩固我的想法， 这是Alaina Kafkes在本文中所建议的。 这有助于我阐明我想谈论的最重要的内容。

Sometimes you start out writing a talk about how brown bears are best, but as you start to sketch out the timeline for what you want to discuss, you realize that you really want to talk about why polar bears are undervalued and really deserve more attention overall.

有时您开始写关于棕熊最好的演讲，但是当您为要讨论的事情勾勒出时间表时，您意识到您真的想谈谈为什么北极熊被低估了，并且确实值得整体关注。

回答问题：为什么我要参加这次演讲？ (Answer the question: why should I attend this talk?)

The abstract you submit is your selling point. The elevator pitch of your talk. It’s like a dating profile to potential matches. Think about the value of your talk to potential attendees, because this is how reviewers will decide whether or not to include it.

您提交的摘要是您的卖点。 您讲话的电梯音调。 这就像潜在比赛的约会资料。 考虑一下您对潜在参与者的演讲的价值，因为这是审阅者将决定是否包括它的方式。

I usually write out a separate section with at least 3 explicit takeaways that I will incorporate into the abstract and often also include that in my description. One of the most common reasons talks get denied is “Can’t think of any takeaways”. As a reviewer, a common litmus test for reading a talk is “Would I have interest in this talk myself?” and if the answer is no, that can be a good reason to favor a different, more compelling proposal instead.

我通常会写出一个单独的部分，至少包含3个明确的要点，然后将这些要点纳入摘要中，并且通常也将其包含在我的描述中。 拒绝对话的最常见原因之一是“想不出任何外卖”。 作为审阅者，阅读演讲的常见石蕊测试是“我自己对此演讲是否会感兴趣？” 如果答案是否定的，那么这可能是赞成另一个更引人注目的提案的充分理由。

考虑一下为什么您是最好的演讲者 (Think about why you are the best person to give this talk)

Saron from Code Newbie gave this advice in a webinar on submitting to conferences that really stuck with me. Don’t submit a talk that should be a blog post. As someone who really loves practical takeaways, I often write talks that feel more like “5 reasons to switch to X framework”, but the best talks have a good story as well.

来自Code Newbie的 Saron在网络研讨会上就如何提交真正困扰我的会议给出了建议。 不要提交应该是博客文章的演讲。 作为一个真正喜欢实用的东西的人，我经常写一些感觉更像是“转向X框架的5个理由”的演讲，但是最好的演讲也有一个很好的故事。

Looking at it from this perspective humanizes my speaking and makes my talks more like a journey than a series of tips that could be easily skimmed. You want to leave your attendees with more than what they would get from a written piece.

从这个角度看待它可以使我的讲话更加人性化，并且使我的演讲更像是一段旅程，而不是一系列可以轻松浏览的技巧。 您想给与会者留下比书面的更多的东西。

请至少一个人阅读您的作品 (Have at least one person read your work)

I always have at least one person review my work and I will continue doing this until the one time when they do not manage to catch something really big. These embarrassing mistakes that I somehow missed in the 50 times I read it myself have included:

我总是至少有一个人来审查我的工作，并且我会继续这样做，直到他们无法捕捉到真正重要的事情为止。 在我自己读过的50本书中，我莫名其妙地错失了这些尴尬的错误，这些错误包括：

• basic spelling errors
  基本拼写错误
• weird auto-correct issues
  奇怪的自动更正问题
• using “I” instead of “me”
  用“我”代替“我”
• choosing a word that didn’t mean what I thought it did
  选择一个不代表我认为的意思的词

This step is really important. To many reviewers, grammatical mistakes both consciously and unconsciously convey a lack of effort.

这一步真的很重要。 对许多评论者而言，语法错误有意识地和无意识地表达了缺乏努力。

得到反馈 (Get feedback)

If the conference offers it, get feedback on proposals! Even if not explicitly stated, when emailing and asking for a second opinion I have never been turned down. This makes a world of difference. Some of the useful feedback I’ve received has included cutting irrelevant subjects, adding more detail to a particular technical explanation, and making the takeaways more obvious.

如果会议提供了建议，请获取建议的反馈！ 即使没有明确说明，在发送电子邮件和征求第二意见时，我也从未拒绝过。 这使世界变得与众不同。 我收到的一些有用的反馈意见包括切掉不相关的主题，在特定的技术说明中增加更多细节，并使要点更加明显。

Best of luck in your journey!

祝您旅途中一切顺利！

Like many things in life, submitting to conferences is a bit of a numbers game, so don’t give up if you are not accepted the first time. Ask them for tips on how to improve! Hope to see you at an event soon.

就像生活中的许多事情一样，参加会议有点像是数字游戏，所以如果您不被第一次接受，请不要放弃。 向他们询问如何改进的提示！ 希望很快见到你。

翻译自: https://www.freecodecamp.org/news/how-to-get-a-technical-talk-accepted-at-a-conference-or-event-8ba291d11c62/

国际大会演讲ppt