I could put together a script and "live-code" in front of my audience. I don't like this so much because it keeps me so busy that it's hard for me to give a good explanation while I write. And there's also a high chance of me causing errors and make them wait.
I like this option, if you can get your demo streamlined to the point of not holding up the audience. You can do what TV cooks do when the recipe takes more time than they have; start the coding, then jump ahead to one that's 90% or 100% done.
If you have a colleague you can get up to speed, you can have them do the coding while you talk and point out what they're doing.
You can use your IDE, which will give the syntax highlighting and show your audience how to compile, deploy, test, etc. I would recommend using an oversized font though, just for the session, so that everyone can see.
您的 IDE 是否允许打开/关闭区域或代码段？ 在 Visual Studio 中，您可以创建可以展开或折叠的代码区域。 如果您的 IDE 能够执行此操作，您可以将代码示例创建为区域，然后在浏览演示文稿时打开/关闭它们。 您可以在 IDE 中的演示文稿和代码示例之间来回切换，但不必即时编码。 使用打开/关闭可以隐藏未引用的代码，以保持事物不那么混乱。
事实上，我在 2008 年敏捷大会上看到了这一点，而且效果似乎相当不错。
Does your IDE allow opening/closing regions or code segments? In Visual Studio you can create code regions that you can expand or collapse. If your IDE has the ability to do this you could create your code samples as regions and then open/close them as you go through your presentation. You could switch back and forth between your presentation and code samples in the IDE, but wouldn't have to code on the fly. Using open/close allows you to hide the code you're not referencing to keep things less cluttered.
I actually saw this done at Agile 2008 and it seemed to work pretty well.
另外，如果程序员熟悉类似的东西，请尝试将所有概念与他们所知道的联系起来。 它使它更容易掌握。 就像如果您正在解释 Spring MVC 并且他们了解 Struts，请解释 Struts 的等效项。 将此类内容以表格形式呈现（甚至作为讲义）可能会很有用。
这正是我所做的（Struts 程序员的 Spring MVC 入门）。
You can only fit so much information on a PowerPoint slide but that's actually a good thing: people can only look at a certain amount of information and get something meaningful from it.
So if you can't fit it on a PowerPoint slide, you need to rethink your approach.
Code snippets are good. They don't need to be highlighted. Just put them in Courier New (or some other fixed width font) and it'll come across as code. Code snippets don't have to be complete either. Just boil them down to the essential concepts (using comments or ellipses to indicate missing code).
Programmers being programmers, they'll probably ask questions when it gets to the technical, which is good.
Also, if the programmers are familiar with something similar try and relate all the concepts back to what they know. It makes it easier to grasp. Like if you're explaining Spring MVC and they know Struts, explain the Struts equivalents. It can be useful to put that sort of thing in table form (even as a handout).
That's what I did for exactly that (a Spring MVC primer for Struts programmers).
If you want your audience to see a lot of code snippets, especially lengthy ones, you could print them out as handouts or provide them as notes in PDF or text files (people can follow along on their laptops).
Actual presentation slides should contain the smallest amount of text (including code) necessary to convey your ideas. If there's a lot to read from a distance, your audience will get tired after awhile and might have trouble following along. Let people read the full code sections on their own laptops or handouts, while calling attention to just the critical parts in your presentation slides or script.
If they don't like Powerpoint, don't use use it. We use Camtasia screen recording to record 'live' demos for presentation to customers (live in quotes since it doesn't have the disadvantage of crashing halfway through your presentation :-). They always prefer to see it in action rather than what they think is fudged functionality.
It's pause-able like your Powerpoint slides and has the advantage of syntax coloring since you just record bringing your up in your favorite editor. It's also dynamic which is much better than Powerpoint (although I've seen some people do crude animation with multiple Powerpoint slides, always funny to watch in action).
This basically maps to your screencast idea but, if you want a reason to be there, do a large number of small screencasts to show interspersed between your real presentation, narrating (in person, not on the screencast) if necessary.
Personally, I'd prefer to send a fully narrated Camtasia off to the target audience but that's because I'm not totally over my early-career phobia of public speaking :-).
In a pinch, you could do a real live demo since your audience (is videance the equivalent for video presentations?) are programmers and will understand any problems you have.
I had this done to me, and thought that it was the best possible solution:
Get another person to help you out. While you are talking about the code, let the helper type the code. This way everyone in the room will be looking at the code, while listening to you explain it.
This of course involves finding someone who can help out, and understand the code just as well as you do. But the results can be great.
If you could do it all in a screencast and you wouldn't have to be there, then do a screencast and don't be there. Nobody complains when a meeting gets canceled. Just distribute the video, maybe with an accompanying report with notes or links so people can read more about the tools you're demonstrating.
And you'll get more credit later as your co-workers and managers talk to other people: "Hey, did you see the presentation Bibac did? No? You should; I'll send you the address after lunch."
If you're demonstrating code in the presentation, then also consider having the finished project available so people can try it for themselves.
当我进行涉及 Visual Studio 的演示时，我将代码片段放在工具箱的常规选项卡上。 在演示过程中，我将这些代码片段拖放到代码文件、标记页面等中。
When I give presentations involving Visual Studio I put code snippets on the general tab of the toolbox. During the presentation I drop/drag these code snippets into a code file, markup page, etc.
发布评论
评论（8）
我喜欢这个选项，如果你能让你的演示精简到不妨碍观众的程度。 当电视厨师做菜比他们花更多时间时，你可以做同样的事情； 开始编码，然后跳转到已完成 90% 或 100% 的编码。
如果您有同事可以跟上进度，您可以让他们在您交谈时进行编码并指出他们在做什么。
您可以使用 IDE，它会突出显示语法并向您的观众展示如何编译、部署、测试等。不过，我建议仅在会话中使用超大字体，以便每个人都可以看到。
I like this option, if you can get your demo streamlined to the point of not holding up the audience. You can do what TV cooks do when the recipe takes more time than they have; start the coding, then jump ahead to one that's 90% or 100% done.
If you have a colleague you can get up to speed, you can have them do the coding while you talk and point out what they're doing.
You can use your IDE, which will give the syntax highlighting and show your audience how to compile, deploy, test, etc. I would recommend using an oversized font though, just for the session, so that everyone can see.
您的 IDE 是否允许打开/关闭区域或代码段？ 在 Visual Studio 中，您可以创建可以展开或折叠的代码区域。 如果您的 IDE 能够执行此操作，您可以将代码示例创建为区域，然后在浏览演示文稿时打开/关闭它们。 您可以在 IDE 中的演示文稿和代码示例之间来回切换，但不必即时编码。 使用打开/关闭可以隐藏未引用的代码，以保持事物不那么混乱。
事实上，我在 2008 年敏捷大会上看到了这一点，而且效果似乎相当不错。
Does your IDE allow opening/closing regions or code segments? In Visual Studio you can create code regions that you can expand or collapse. If your IDE has the ability to do this you could create your code samples as regions and then open/close them as you go through your presentation. You could switch back and forth between your presentation and code samples in the IDE, but wouldn't have to code on the fly. Using open/close allows you to hide the code you're not referencing to keep things less cluttered.
I actually saw this done at Agile 2008 and it seemed to work pretty well.
一张 PowerPoint 幻灯片上只能容纳这么多信息，但这实际上是一件好事：人们只能查看一定量的信息并从中获取有意义的内容。
因此，如果您无法将其放入 PowerPoint 幻灯片中，则需要重新考虑您的方法。
代码片段很好。 它们不需要突出显示。 只需将它们放入 Courier New（或其他固定宽度字体）中，它就会显示为代码。 代码片段也不必是完整的。 只需将它们归结为基本概念（使用注释或省略号来指示缺失的代码）。
程序员就是程序员，当涉及到技术问题时，他们可能会提出问题，这很好。
另外，如果程序员熟悉类似的东西，请尝试将所有概念与他们所知道的联系起来。 它使它更容易掌握。 就像如果您正在解释 Spring MVC 并且他们了解 Struts，请解释 Struts 的等效项。 将此类内容以表格形式呈现（甚至作为讲义）可能会很有用。
这正是我所做的（Struts 程序员的 Spring MVC 入门）。
You can only fit so much information on a PowerPoint slide but that's actually a good thing: people can only look at a certain amount of information and get something meaningful from it.
So if you can't fit it on a PowerPoint slide, you need to rethink your approach.
Code snippets are good. They don't need to be highlighted. Just put them in Courier New (or some other fixed width font) and it'll come across as code. Code snippets don't have to be complete either. Just boil them down to the essential concepts (using comments or ellipses to indicate missing code).
Programmers being programmers, they'll probably ask questions when it gets to the technical, which is good.
Also, if the programmers are familiar with something similar try and relate all the concepts back to what they know. It makes it easier to grasp. Like if you're explaining Spring MVC and they know Struts, explain the Struts equivalents. It can be useful to put that sort of thing in table form (even as a handout).
That's what I did for exactly that (a Spring MVC primer for Struts programmers).
如果您希望观众看到大量代码片段，尤其是冗长的代码片段，您可以将它们打印为讲义，或者以 PDF 或文本文件的形式提供注释（人们可以在笔记本电脑上跟随）。
实际的演示幻灯片应包含传达您的想法所需的最少量的文本（包括代码）。 如果有很多内容需要从远处阅读，您的听众在一段时间后就会感到疲倦，并且可能会难以跟上。 让人们在自己的笔记本电脑或讲义上阅读完整的代码部分，同时吸引人们注意演示幻灯片或脚本中的关键部分。
If you want your audience to see a lot of code snippets, especially lengthy ones, you could print them out as handouts or provide them as notes in PDF or text files (people can follow along on their laptops).
Actual presentation slides should contain the smallest amount of text (including code) necessary to convey your ideas. If there's a lot to read from a distance, your audience will get tired after awhile and might have trouble following along. Let people read the full code sections on their own laptops or handouts, while calling attention to just the critical parts in your presentation slides or script.
如果他们不喜欢 Powerpoint，就不要使用它。 我们使用 Camtasia 屏幕录制来录制“实时”演示，以便向客户演示（实时报价，因为它不存在演示中途崩溃的缺点:-）。 他们总是更喜欢看到它的实际效果，而不是他们认为捏造的功能。
它像 Powerpoint 幻灯片一样可以暂停，并且具有语法着色的优点，因为您只需在您最喜欢的编辑器中记录您的想法。 它也是动态的，这比 Powerpoint 好得多（尽管我见过有些人用多张 Powerpoint 幻灯片制作粗糙的动画，观看时总是很有趣）。
这基本上映射到你的截屏视频想法，但是，如果你想要一个理由，可以做大量的小截屏视频，穿插在你的真实演示之间，如有必要，可以进行旁白（亲自，而不是在截屏视频上）。
就我个人而言，我更愿意向目标受众发送一个完整叙述的 Camtasia，但那是因为我还没有完全克服我职业生涯早期对公开演讲的恐惧:-)。
在紧要关头，您可以进行真正的现场演示，因为您的观众（视频演示相当于视频演示吗？）是程序员，并且会理解您遇到的任何问题。
If they don't like Powerpoint, don't use use it. We use Camtasia screen recording to record 'live' demos for presentation to customers (live in quotes since it doesn't have the disadvantage of crashing halfway through your presentation :-). They always prefer to see it in action rather than what they think is fudged functionality.
It's pause-able like your Powerpoint slides and has the advantage of syntax coloring since you just record bringing your up in your favorite editor. It's also dynamic which is much better than Powerpoint (although I've seen some people do crude animation with multiple Powerpoint slides, always funny to watch in action).
This basically maps to your screencast idea but, if you want a reason to be there, do a large number of small screencasts to show interspersed between your real presentation, narrating (in person, not on the screencast) if necessary.
Personally, I'd prefer to send a fully narrated Camtasia off to the target audience but that's because I'm not totally over my early-career phobia of public speaking :-).
In a pinch, you could do a real live demo since your audience (is videance the equivalent for video presentations?) are programmers and will understand any problems you have.
我做了这件事，并认为这是最好的解决方案：
找另一个人来帮助你。 当您谈论代码时，让助手输入代码。 这样房间里的每个人都会一边看代码，一边听你解释。
当然，这需要找到可以提供帮助并像您一样理解代码的人。 但结果可能会很棒。
I had this done to me, and thought that it was the best possible solution:
Get another person to help you out. While you are talking about the code, let the helper type the code. This way everyone in the room will be looking at the code, while listening to you explain it.
This of course involves finding someone who can help out, and understand the code just as well as you do. But the results can be great.
如果你可以在截屏视频中完成这一切，而你不必在那里，那么就做一个截屏视频，但不要在那里。 当会议被取消时，没有人抱怨。 只需分发视频，也许还附有带有注释或链接的随附报告，以便人们可以阅读有关您演示的工具的更多信息。
当你的同事和经理与其他人交谈时，你会得到更多的信任：“嘿，你看到 Bibac 所做的演示了吗？没有？你应该看到；午餐后我会把地址发给你。”
如果您在演示文稿中演示代码，那么还可以考虑提供已完成的项目，以便人们可以自己尝试。
If you could do it all in a screencast and you wouldn't have to be there, then do a screencast and don't be there. Nobody complains when a meeting gets canceled. Just distribute the video, maybe with an accompanying report with notes or links so people can read more about the tools you're demonstrating.
And you'll get more credit later as your co-workers and managers talk to other people: "Hey, did you see the presentation Bibac did? No? You should; I'll send you the address after lunch."
If you're demonstrating code in the presentation, then also consider having the finished project available so people can try it for themselves.
当我进行涉及 Visual Studio 的演示时，我将代码片段放在工具箱的常规选项卡上。 在演示过程中，我将这些代码片段拖放到代码文件、标记页面等中。
When I give presentations involving Visual Studio I put code snippets on the general tab of the toolbox. During the presentation I drop/drag these code snippets into a code file, markup page, etc.