BobMcGee123

One of my professors has enlisted me to give a programming presentation to the programming class here where I go to school. I'm going to be discussing the physical model I use to simulate a hovercraft air cushion vehicle.

I've never done this before, so I'm somewhat nervous. I'm mostly just afraid that nobody will really care what I'm doing.

Anyway, I've discussed a basic plan with my professor, and this is essentially what the presentation will cover. It will likely take two classes to present.

-What is an air cushion vehicle? (slide1)
-What aspects am I trying to simulate in my simulation (slide 2)
-Show the computer program in action
-Discuss the code modules at the objective theoretical level (slide 3)
-Discuss specific algorithms and math, e.g. the physical model, what data is passed to the numerical solver, how do I accomplish the collision model, how do I test the validity of an algorithm, etc.

This is the same professor that is trying to start an organization with two MIT students, and now me, to write efficient and 'easier' surfacing software for machines that fabricate propellors (there is not really an effective streamlined way of going from the design phase of propellor fabrication to then instructing a machine to fabricate the part...the whole process is currently cumbersome, he wants to call this 'open prop').

Just thought I'd share...I'll tell you how it goes. If nothing else this ........ will look good on a resume.

__________________
argus triad mingus

Mario F.

Well, good luck Bob. Keep those nerves controlled and all will be well. All the best.

__________________
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.

indigo0086

Blow them away! *pun*

twomers

Have you ever presented anything before?

__________________
I blag!

BobMcGee123

Not anything that I actually cared about.

__________________
argus triad mingus

SlyMaelstrom

Once he presented his "masculinity" to a woman, but he didn't quite get the response he expected.

I wish you much more luck with this one, Bob.

__________________

Terms of Service

ahluka

Film it.

__________________
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.

- Mike McShaffry

maxorator

Don't show them that you're scared or they will bite.

__________________
The duck is irrelevant to my point.

BobMcGee123

Haha, yeah, that's what I was going to say!!!

I'm not really scared about presenting, when it comes right down to it I don't really care what they think, it's just that I'm actually interested in the topic. What I'm afraid of is that the class will just be made up of people that are forced to take the class and aren't particularly interested in my subject matter. But, well, whatever.

I don't know if I can film it or not, I'll look into it, but it probably won't happen.

__________________
argus triad mingus

Sentral

While your in the middle of your presentation pull out a gun, and shoot yourself. Budd Dwyer style!

Good luck!!

__________________
Videogame Memories!
A site dedicated to keeping videogame memories alive!

http://www.videogamememories.com/
Share your experiences with us now!

"We will game forever!"

twomers

Yeah. Don't forget to imagine the people you're presenting to in your underwear ...

__________________
I blag!

Perspective

1. You're going to talk too fast. Slow down, pace yourself, and take the time to explain details, even if they seem obvious.

2. People will care so long as you have pretty screen shots.
... 2.1 Diagrams are a great way to explain things
... 2.2 If your slides have too much text, no one will read them

3. Pretend you're relaxed. If you act nervious your audience will feel nervous, if you act relaxed your audience will feel relaxed.
... 3.1 I like talking to the audience as if they were one friend sitting with me, very casual. It comes accross well but this is a preference thing. Some people like to be more formal.

4. Back to point one, you started talking fast again and didn't even notice... slow down

__________________
jeff.bagu.org - Terrain rendering and other random stuff

manutd

I like screenshots...But seriously, good luck! Record the screens for us

__________________
Silence is better than unmeaning words.
- Pythagoras
My blog

BobMcGee123

Good suggestions per, and yeah the talking way too fast thing definitely applies to me. I told the professor to interrupt me and ask lots of questions because I *know* beyond a reasonable doubt I'll start to get off track, ramble quickly, etc.

EDIT:
And don't have your presentation be what is on the slides...I hate it when professors give a powerpoint, and all they do is read the slide to us. My slides are basically just index cards that tell me to remember what to talk about (to guide my ramblings). But only as a guide.

__________________
argus triad mingus

Dave_Sinkula

In addition to some of the advice previously mentioned, I once found a cheat for myself: bringing a glass of water. I get cottonmouthed anyways, but it also helps slow you down and relax.

Then, like Perspective said, pretend you are talking to some friends. I might even try to go with "like you're talking to your mom or some not-so-technical friends" -- at least in part. That can help you "cut to the chase" a bit. Which is to say, you are talking about something that interests you: help your audience get interested by sharing this with them.

So...

• Brief non-technical "executive summary". Why is this interesting?
  
• What is an air cushion vehicle? (slide1)
• The basics: what did you have to start with? Why was it insufficient?
  
• What aspects am I trying to simulate in my simulation (slide 2)
• Folksy again: a not-so-technical brief of the problems that influenced your code development.
  
• Show the computer program in action
• Re-draw interest by pointing out what your stuff does that the starting stuff didn't or had issues with.
  
• Discuss the code modules at the objective theoretical level (slide 3)
• Again mention the specific issues with available material as well as with what you've got.
  
• Discuss specific algorithms and math, e.g. the physical model, what data is passed to the numerical solver, how do I accomplish the collision model, how do I test the validity of an algorithm, etc.
• Again mention the specific issues with available material as well as with what you've got.

Something like that, as a suggestion. I like it when a presenter goes back-and-forth from technical to not-so-technical -- it keeps me interested.

The stuff that just goes deeper and deeper into technical issues puts me to sleep, especially when it's the monologue of "this one thing only" rather than somewhat of a discussion of related items (some of which I may find familiar to regain my attention).

And yeah, try to avoid reading the slides. I do that too much even when I'm trying not to.

__________________
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*