blocks|key|1130940|text|在代码中添加有趣的注释。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1130941|//在我的下一次演示中最好不要失败，愚蠢的@#$@#%25$代码。|1130942|不要谈论他们，让他们被观众发现。|1130943|-Adam|1130944|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Put interesting comments in the code.

// This better not fail during my next presentation, stupid @#$@#%$ code.

Don't talk about them, let them be found by the audience.

-Adam

blocks|key|828564|text|FYI，Hanselman的文章有更新+(您的链接是从2003年开始的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828565|entityMap|0|LINK|mutability|MUTABLE|url|http://www.hanselman.com/blog/11TopTipsForASuccessfulTechnicalPresentation.aspx^0|H|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

FYI, that Hanselman article has <a href="http://www.hanselman.com/blog/11TopTipsForASuccessfulTechnicalPresentation.aspx" rel="nofollow noreferrer">an update</a> (your link is from 2003).

blocks|key|1131142|text|我推荐Scott的职位(前面提到过)。我写了一篇贴士文章，主要是出于自私的原因--我每次在做技术性演讲之前都会回顾一下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131143|技术演示的技巧|offset|length|1131144|如果使用控制台提示符，确保字体是可读的，并且在可能的情况下你的路径是预先设定的。。|1131145|花15分钟安装和学习使用ZoomIt，这样你的观众就能清楚地看到你在炫耀什么。如果你要问他们是否能看到什么，你已经失败了。|1131146|也许最重要的是有单独的Visual设置，预先配置了大的、可读的字体。|1131147|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/jgalloway/archive/2006/12/05/tips-for-a-technical-presentation.aspx|1|http://weblogs.asp.net/jgalloway/archive/2007/07/09/presentation-tricks-command-windows.aspx|2|https://technet.microsoft.com/en-us/sysinternals/zoomit.aspx|3|http://technet.microsoft.com/zh-cn/sysinternals/bb897434(en-us).aspx)^0|0|0|7|0|0|B|T|1|0|C|6|2|0|7|Q|3|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@$D|1D|E|1E|1|1F]]|A|$]]|$1|L|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]|X|$5|O|P|Q|A|$R|Y]]]]

I recommend Scott Hanselman's post (previously mentioned). I've written up a post with some tips, mostly for selfish reasons - I review it every time before I give a technical presentation:

<a href="http://weblogs.asp.net/jgalloway/archive/2006/12/05/tips-for-a-technical-presentation.aspx" rel="nofollow noreferrer">Tips for a Technical Presentation</a>

If you're using a console prompt, <a href="http://weblogs.asp.net/jgalloway/archive/2007/07/09/presentation-tricks-command-windows.aspx" rel="nofollow noreferrer">make sure the font is readable and that your paths are preset when possible</a>.

Take 15 minutes to install and learn to use <a href="https://technet.microsoft.com/en-us/sysinternals/zoomit.aspx" rel="nofollow noreferrer">ZoomIt</a>, so your audience can clearly see what you're showing off. If you have to ask if they can see something, you've already failed.

Probably most important is to <a href="http://technet.microsoft.com/zh-cn/sysinternals/bb897434(en-us).aspx" rel="nofollow noreferrer">have separate Visual Studio settings pre-configured with big, readable fonts</a>.

blocks|key|132382|text|我从演示中得到的最好的建议之一是，事先简单地录下来，然后播放视频，现场讲述。然后，意想不到的事情发生在私下，你得到了很多刺伤，你需要它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132383|你通常仍然需要一些环境来作为问题的参考，但是对于演示部分来说，提前录制它(并在视频上排练你的叙述)可以保证你可以处于游戏的顶端。|132384|我也喜欢在幻灯片里放一些小笑话，那些录像让人看起来像是幻灯片的作者在现场评论，或者说是其他人在运行幻灯片。经常，我一点也不提幻灯片上的笑话。|132385|例如，在我的最近的演示介绍中，我看到了以"ASP.NET+MVC“为中心的幻灯片，其中谈到了我是如何使用框架的。以较小的字体，我的文字“吸引人的名字，是吧？”当我现场演示的时候，那张幻灯片被人笑了。这不值得任何想象，但我们经常呈现一些相当干燥的东西，每一点都有帮助。|offset|length|132386|类似地，我还包括了一些幻灯片，这些幻灯片只是屏幕外的那个家伙对我计划说的话的尖刻评论。所以，我会说，“这个项目的代码库需要一点帮助”，而在我身后的幻灯片上写着“实际上是一堆有3个肉丸的意大利面”和一盘意大利面作为幻灯片的背景。再一次，我没有发表任何评论，只是继续看下一张幻灯片，就好像我根本没看过它一样让它变得更有趣了。|132387|如果你没有最佳的喜剧时机，在减轻压力的同时还能增加一些轻浮，那也是有帮助的。|132388|不管怎么说，说到底，我一直在做我的大部分演示/演示工作，就像我会做的那样，如果它是一个屏幕，然后用我的现场版本(如果事情不正常的话，可以暂停视频)代替音频，当我在观众面前给它的时候。|132389|当然，你可以很容易地将真正的演示文稿提供给那些想要它的人。|132390|对于幻灯片，我通常不会经常在屏幕上说出确切的单词。|132391|entityMap|0|LINK|mutability|MUTABLE|url|http://www.wynia.org/wordpress/2008/09/07/standardized-aspnet-mvc-controller-actions-with-visual-studio-item-templates/^0|0|0|0|6|7|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@$H|15|I|16|1|17]]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1C|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

One of the best pieces of advice I ever got for doing demos is to just plain record them in advance and play back the video, narrating live. Then the unexpected stuff happens in private and you get as many stabs at it as you need.

You still usually need some environment to use as a reference for questions, but for the presentation bit, recording it in advance (and rehearsing your narration over the video) pretty much guarantees you can be at the top of your game.

I also like to put small jokes into the slides and that recorded video that make it seem like the person who made the slides is commenting on the live proceedings or that someone else is actually running the slides. Often, I make absolutely no reference at all to the joke in the slide.

For instance, in my <a href="http://www.wynia.org/wordpress/2008/09/07/standardized-aspnet-mvc-controller-actions-with-visual-studio-item-templates/" rel="nofollow noreferrer">most recent demo presentation</a>, I had a slide with the text "ASP.NET MVC" centered that I was talking over about how I was using the framework. In a smaller font, I had the text "Catchy name, huh?". When I did that demo live, that slide got a chuckle. It's not stand-up worthy by any stretch of the imagination, but we're often presenting some pretty dry stuff and every little bit helps.

Similarly, I've included slides that are just plain snarky comments from the offscreen guy about what I'm planning to say. So, I'll say, "The codebase for this project needed a little help", while the slide behind me said "It was a pile of spaghetti with 3 meatballs, actually" and a plate of spaghetti as the slide background. Again, with no comment from me and just moving on to the next slide as though I didn't even see it actually made it funnier.

That can also be a help if you don't have the best comedic timing by taking the pressure off while still adding some levity.

Anyway, what it really comes down to is that I've been doing most of my demo/presentation work just like I would if it was a screencast and then substituting the live version of me (pausing the video as appropriate if things go off the rails) for the audio when I give it in front of an audience.

Of course, you can then easily make the real presentation available afterward for those who want it. 

For the slides, I generally go out of my way to not say the exact words on the screen more often than not.

blocks|key|132410|text|如果您正在显示为您准备的代码，那么请确保它能够正常工作。我知道这是一个显而易见的问题，但我只是在一个会议上，5个发言者中有4个出现了代码问题。告诉我它是‘酷’，甚至‘非常酷’，当它不工作时，这是一个艰难的推销。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132411|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are showing code that was prepared for you then make sure you can get it to work. I know this is an obvious one but I was just at a conference where 4 out of 5 speakers had code issues. Telling me it is 'cool' or even 'really cool' when it doesn't work is a tough sell.

blocks|key|1131027|text|你应该阅读马克·杰森·多米尼克关于公共演讲的出色报告：会议介绍柔道|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1131028|entityMap|0|LINK|mutability|MUTABLE|url|http://plover.com/|1|http://perl.plover.com/yak/presentation/^0|5|A|0|R|6|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You should read <a href="http://plover.com" rel="nofollow noreferrer">Mark Jason Dominus</a> excellent presentaton on public speaking:
<a href="http://perl.plover.com/yak/presentation/" rel="nofollow noreferrer">Conference Presentation Judo</a>

blocks|key|1131343|text|对我来说，第一条规则是:不要表现得太多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131344|在几个星期的时间里，你很容易接受一段代码，然后想：“该死，当我给他们看的时候，他们会吓坏的！”即使在你的私人彩排中，你也会对事情感觉很好。但一旦在观众面前，你的代码的复杂性乘以观众人数的平方。(为每个观众成员解释代码变得非常困难了！)|1131345|看似简单而直接的事情，私下里很快就变成了一大碗意大利面，在压力下甚至连你都不明白。不要试图显示生产代码(良好的因素和良好的分区)，制作简单的内联示例来传达您的核心信息。|1131346|我的规则#1可以被愤世嫉俗的人理解为不要高估你的观众。作为一个乐观主义者，我认为不要高估你解释代码的能力！|1131347|rp|1131348|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

The #1 rule for me is: Don't try to show too much. 

It's easy to live with a chunk of code for a couple of weeks and think, "Damn, when I show 'em this they are gonna freak out!" Even during your private rehearsals you feel good about things. But once in front of an audience, the complexity of your code is multiplied by the square of the number of audience members. (It becomes exponentially harder to explain code for each audience member added!)

What seemed so simple and direct privately quickly turns into a giant bowl of spaghetti that under pressure even you don't understand. Don't try to show production code (well factored and well partitioned), make simple inline examples that convey your core message. 

My rule #1 could be construed, by the cynical, as don't overestimate you audience. As an optimist, I see it as don't overestimate your ability to explain your code! 

rp

blocks|key|132452|text|因为这听起来像是你在做现场演示，在这里你将使用真正的系统，而不仅仅是图表(PPT，印象深刻，什么的)，确保它在你开始之前都能工作。它从来没有失败，如果我不尝试在我开始说话之前，它不工作，我期望它。尤其是演示。(我周二要做一次，这样我就能感觉到。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132453|另一件事就是简单地练习，练习，练习。特别是如果您可以在您将要呈现的确切环境中这样做的话。这样你就能感觉到你需要去的地方，这样就不会妨碍你的听众的视图，以及任何其他的技术问题，比如房间设置或系统。|132454|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Since it sounds like you are doing a live presentation, where you will be working with real systems and not just charts (PPT, Impress, whatever) make sure it is all working just before you start. It never fails, if I don't try it just before I start talking, it doesn't work how I expected it to. Especially with demos. (I'm doing one on Tuesday so I can relate.)

The other thing that helps is simply to practice, practice, practice. Especially if you can do it in the exact environment you will be presenting in. That way you get a feel for where you need to be so as not to block the view for your listeners as well as any other technical gotchas there might be with regards to the room setup or systems.

blocks|key|132002|text|这是向我解释的，我认为这是非常有用的。你可能要考虑不要在一开始就滑得很重。你想给听众看一些东西(显然不是代码)，让他们坐在座位的边缘，想知道怎么做你刚才给他们看的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132003|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This is something that was explained to me, and I think it is very useful. You may want to consider not going to slide heavy at the beginning. You want to show your listeners something (obviously probably not the code) up front that will keep them on the edge of their seats wanting to learn about how to do what you just showed them.

blocks|key|132123|text|最近，我开始使用Mind工具进行演示，并发现它进行得非常好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132124|地图|offset|length|132125|基本上，我发现人们只是在你开始详细介绍演讲的那一刻就把它划出来了。用思维地图传递信息(至少在我的经验中)，为信息的传递和绑定提供了一种更容易的方法。|132126|关键是分阶段呈现信息(即，你的高层想法，然后更详细，一次一个)。思维映射工具基本上可以让你扩展你的地图，因为观众观看和你现在越来越详细的信息。这样做可以让你的听众在较小的阶段逐渐吸收数据，这往往有助于保持。|132127|查看FreeMind，以获得一个可以使用的免费工具。心理经理是一款付费产品，但它更精致、更流畅。|132128|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Mind_map|1|http://en.wikipedia.org/wiki/FreeMind|2|http://www.mindjet.com/products/mindmanager_pro/default.aspx^0|0|0|2|0|0|0|0|2|8|1|Q|4|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]|$D|18|E|19|1|1A]]|A|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]]]

I've recently started to use Mind Mapping tools for presentations and found that it goes over very well.

<a href="http://en.wikipedia.org/wiki/Mind_map" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Mind_map</a>

Basically, I find people just zone out the second you start to go into details with a presentation. Conveying the information with a mind map (at least in my experience), provides a much easier way for the information to be conveyed and tied together.

The key is presenting the information in stages (ie, your high-level ideas first, then in more detail, one at a time). The mind-mapping tools basically let you expand your map, as the audience watches and your present more and more detailed information. Doing it this way lets your audience gradually absorb the data in smaller stages, which tends to aid retention.

Check out <a href="http://en.wikipedia.org/wiki/FreeMind" rel="nofollow noreferrer">FreeMind</a> for a free tool to play with. <a href="http://www.mindjet.com/products/mindmanager_pro/default.aspx" rel="nofollow noreferrer">Mind Manager</a> is a paid product, but is much more polished and fluent.

blocks|key|828617|text|保持您的“视觉表现”的简单和标准。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|828618|如果你在Vista上，隐藏你的桌面图标并使用默认的壁纸之一。将您的Visual设置(特别是工具栏)保持为标准，并尽可能“开箱即用”。您在环境中显示的自定义越多，人们就越有可能关注这些内容而不是您的内容。|828619|尽量保持幻灯片上的内容。记住，你是在和你的听众讲话(在最好的情况下)，所以幻灯片应该作为讨论的重点。如果你想要包括更多的细节，把他们放在幻灯片笔记。这是特别好的，如果你使滑板后可用。|828620|如果有人问你一个问题，而你不知道答案，不要害怕说你不知道。这总比猜测你认为答案应该是什么要好。|828621|另外，如果您正在使用Vista，一定要将其放在“演示模式”中。PowerPoint也有类似的模式，所以一定要使用它--在一个监视器(投影机)上有幻灯片放映，还有幻灯片的较小视图，以及笔记本显示器上的便条和计时器。|828622|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Keep your "visual representation" simple and standard.

If you're on Vista hide your desktop icons and use one of the default wallpapers. Keep your Visual Studio settings (especially toolbars) as standard and "out of the box" as possible. The more customizations you show in your environment the more likely people are going to focus on those rather than your content.

Keep the content on your slides as consisce as possible. Remember, you're speaking to (and in the best scenario, with) your audience so the slides should serve as discussion points. If you want to include more details, put them in the slide notes. This is especially good if you make the slide decks available afterwards.

If someone asks you a question and you don't know the answer, don't be afraid to say you don't know. It's always better than trying to guess at what you think the answer should be.

Also, if you are using Vista be sure to put it in "presentation mode". PowerPoint also has a similar mode, so be sure to use it as well - you have the slide show on one monitor (the projector) and a smaller view of the slide, plus notes and a timer on your laptop monitor.

blocks|key|132273|text|你听说过Pecha-Kucha？吗|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|132274|Pecha背后的想法是保持演讲简洁，提高兴趣水平，并让许多演讲者在一个晚上的过程中分享他们的想法。因此，创建了20x20PechaKucha格式:允许每个演示者显示20个图像的幻灯片，每个图像显示20秒。结果是，在下一位演讲者结束之前，在舞台上的总演示时间为6分40秒。|blockquote|132275|现在，我不确定这么短的时间是否可以用于产品演示。但是你可以试着从这个概念中得到一些好的想法，比如简明扼要，保持重点，有效的时间，空间管理等。|132276|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Pecha_Kucha^0|4|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|V|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Have you heard of <a href="http://en.wikipedia.org/wiki/Pecha_Kucha" rel="nofollow noreferrer">Pecha-Kucha?</a>

<blockquote>
 The idea behind Pecha Kucha is to keep
 presentations concise, the interest
 level up and to have many presenters
 sharing their ideas within the course
 of one night. Therefore the 20x20
 Pecha Kucha format was created: each
 presenter is allowed a slideshow of 20
 images, each shown for 20 seconds.
 This results in a total presentation
 time of 6 minutes 40 seconds on a
 stage before the next presenter is up
</blockquote>

Now, i am not sure if that short duration could be ok for a product demonstration. 
But you can try to get some nice ideas from the concept, such as to be concise and keep to the point, effective time, space management etc..

blocks|key|832801|text|除了一些软件如Manager来展示您的架构，您还可以找到一个屏幕记录器作为演示工具来演示您的技术任务。DemoCreator将是一个很好的东西来制作你在屏幕上活动的视频。您可以添加更多的标注，以使这个过程更容易理解。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|832802|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sameshow.com/demo-creator.html#107^0|1F|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Besides some software like Mind Manager to show your architecture, you make find a screen recorder as a presentation tool to illustrate your technical task. <a href="http://www.sameshow.com/demo-creator.html#107" rel="nofollow noreferrer">DemoCreator</a> would be something nice to make video of your onscreen activity. And you can add more callout to make the process easier to understand.

blocks|key|832724|text|如果您使用幻灯片，请遵循盖伊川崎的10/20/30规则|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|832725|不超过10张幻灯片|unordered-list-item|832726|在幻灯片上不超过20分钟|832727|幻灯片上不少于30分的类型|832728|-Adam|832729|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.guykawasaki.com/2005/12/the_102030_rule.html^0|C|F|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$]]|$1|G|3|H|5|F|7|Z|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|10|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

If you use slides at all, follow <a href="http://blog.guykawasaki.com/2005/12/the_102030_rule.html" rel="nofollow noreferrer">Guy Kawasaki's 10/20/30 rule</a>:

<ul>
<li>No more than 10 slides</li>
<li>No more than 20 minutes spent on slides</li>
<li>No less than 30 point type on slides</li>
</ul>

-Adam

I am planning to give a Technical presentation for a product we are building.
Intended audience is Technical developers. So, most of the time, I will be debugging trough the code in Visual Studio, performance analysis, some architecture review etc.

I have read couple of <a href="http://www.hanselman.com/blog/11TopTipsForASuccessfulTechnicalPresentation.aspx" rel="nofollow noreferrer">blogs</a> on font sizes to use, templates to use on Visual Studio, <a href="http://weblogs.asp.net/jgalloway/archive/2006/12/05/tips-for-a-technical-presentation.aspx" rel="nofollow noreferrer">presentation tools</a>, <a href="http://focs.wordpress.com/2007/09/12/9-tips-how-to-give-a-technical-presentation/" rel="nofollow noreferrer">among other</a> very <a href="http://blogs.msdn.com/kaevans/archive/2005/03/12/394527.aspx" rel="nofollow noreferrer">useful tips</a>.

What I am looking specifically for is how to keep the session interesting without making it a dry code walkthrough? How to avoid making people fall asleep? Would be great to hear some stories..

Update1: Nice youtube clip on zoomit. <a href="http://www.youtube.com/watch?v=4jMLAF-9ACk" rel="nofollow noreferrer">Glue Audience To Your Presentation With Zoomit.</a>

Update2: New post from Scott Hanselman after his <a href="http://channel9.msdn.com/pdc2008/TL49/" rel="nofollow noreferrer">PDC talk</a> - <a href="http://www.hanselman.com/blog/TipsForPreparingForATechnicalPresentation.aspx" rel="nofollow noreferrer">Tips for Preparing for a Technical Presentation</a>

Good tips for a Technical presentation

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我计划为我们正在生产的产品做一次技术演示。预期的受众是技术开发人员。因此，在大多数情况下，我将通过Visual中的代码、性能分析、一些体系结构审查等进行调试。我读过几个关于字体大小的，在Visual上使用的模板，， very 。我特别要寻找的是如何保持会话的趣味性，而不让它成为一个枯燥的代码演练？如何避免让人入睡？很高兴听到一些故事..。Update1：很棒的youtube在动物园里的剪辑。Upd

问技术演示的好提示
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问技术演示的好提示EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问技术演示的好提示
EN