From: luis fernandes <elf@ee.ryerson.ca>
Cc: ding@gnus.org
Subject: The Talk
Date: Sun, 4 Oct 1998 14:35:01 -0400 [thread overview]
Message-ID: <199810041835.OAA06084@ryerson.ca> (raw)
In-Reply-To: <m3lnmykw98.fsf@sparky.gnus.org>
The rule of thumb I use for my presentations is 1 overhead per minute
of talking. I find that having overheads or other multi-media aids
makes for less boring talks than just talking straight. Note that my
audience has usually been 2nd to 4th year electrical engineering
students with short attention spans.
So, if you converted your script into overhead slides (bulleted,
point-form text using 12-14pt Helvetica), you should have roughly 45
slides.
I have a LaTeX template for overhead slides I dug out of the CTAN
archives, if you want it.
next prev parent reply other threads:[~1998-10-04 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-03 6:14 Lars Magne Ingebrigtsen
1998-10-03 20:48 ` Harry Putnam
1998-10-03 21:50 ` Stefanie Teufel
1998-10-03 22:58 ` Manoj Srivastava
1998-10-04 0:43 ` Harry Putnam
1998-10-04 18:35 ` luis fernandes [this message]
1998-10-05 14:29 ` Anders Melchiorsen
1998-10-06 6:06 ` Lars Magne Ingebrigtsen
1998-10-06 15:05 ` John H Palmieri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199810041835.OAA06084@ryerson.ca \
--to=elf@ee.ryerson.ca \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).