Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When I was working on my doctorate, the faculty gave us this rule for seminars - and it has proved very useful since:</p> <ol> <li>Tell 'em what you're gonna tell 'em. (E.g., brief introductory problem description and results abstract)</li> <li>Tell 'em. (E.g. technical details comprising the bulk of the time)</li> <li>Tell 'em what you told 'em. (E.g. brief summary and conclusions)</li> <li>Open the floor for questions.</li> </ol> <p>In your position, I would take about 10-20% of your allotted time to do #1 in a largely non-technical way. So you might describe the business function your code automates, why that's important, what things were like before and after applying your solution, how it's saving money, that kind of thing.</p> <p>Then I'd launch into a highly technical discussion aimed at the CS/SE crowd. Even if the rest of the folks don't understand it and their eyes glaze over, your introduction at least will have given them a sense of what it's all about, and they might recognize a bit here or there.</p> <p>For the third part, I'd briefly recap the problem and describe how you solved it in non-technical language, and then do your live-coding extensibility whiz-bang demo. Even if the non-CS/SE folks don't understand the demo, they'll see eye candy flying by and your professional peers and faculty all nodding and smiling, so they'll think it's cool.</p> <p>I once attended a seminar by a guy who won the Nobel Prize for applying chaos theory to chemical systems. He applied this approach, so even though all the non-theoreticians like my fellow organic chemists and I were all completely out of our depth, the fact that the theoreticians were all excited left us feeling like it was a great seminar even though we didn't have a clue about what he'd said.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COThis guys got it: "been there / done that". But I need to add that the first time you get in front of a large group - somewhere over 50 - 100 or larger, there is a mental lockup that comes from all the attention suddenly on you. Two tools can overcome this: 1 - be interested in what you are talking about + keep your focus on what it is you have to say. 2 - Go to Tostmasters and do a few public speaking trials, that is exactly what they are for.
      singulars
    2. CONicholas is right: get some practice. Grab a few of your fellow students (bribed with food/drink if suitable) and give your talk at least once, preferably twice, and get feedback. Also, when you give your talk "for real", excitement and/or nervousness may lead you to talk more rapidly than normal, leading to a shortened talk. So try to speak a little more slowly than you feel like doing, enunciate carefully, mark your notes with target times to reach the major sections, check a watch you stuck on the podium from time to time, and speed up or slow down as needed.
      singulars
    3. COYes Bob, and be sure to tell op not to mention bribery, piracy or deeply arcane intrusion issues - those tend to get the thinking of the audience going into stressors. When and if you do lock-up, the canonical recovery to chose one person in the audience and speak directly to that person. That's what the pro's do - it keeps things moving. A totally frozen speaker gets rejected.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload