Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re: (OT) Presentations Involving Code

by xdg (Monsignor)
on Mar 07, 2007 at 21:00 UTC ( #603718=note: print w/replies, xml ) Need Help??

in reply to (OT) Presentations Involving Code

My question is this: How best can a person present code?

Personally, I'd think of great presentations you've seen and try to emulate them. As a fallback, look at how others have presented code in Perl. I'd recommend looking at slides from Perl conferences in the past. In searching for links to some, I also came across dominus' Conference Presentation Judo talk, which you may find useful.

If I have to give one major tip, use big fonts. 3 - 5 lines of code on a presentation slide (and really, really big) is probably all that you can count on being legible to everyone in the audience.


Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Replies are listed 'Best First'.
Re^2: (OT) Presenations Involving Code
by wazoox (Prior) on Mar 07, 2007 at 21:37 UTC
    Yes, dominus' presentation judo is really great; even if it doesn't fit your need, at least it's hilarious :)
Re^2: (OT) Presenations Involving Code
by vrk (Chaplain) on Mar 08, 2007 at 09:20 UTC
    3 - 5 lines of code on a presentation slide (and really, really big) is probably all that you can count on being legible to everyone in the audience.

    Since you're not given even twenty lines for each function but five lines for the whole program, the best way to get it all fit the slide is, of course, to golf!

    On a more serious note, I agree with this: put the key points on the slides, and very, very little cruft. No-one wants to read long slides. What this means with code depends on the case, but I would say removing error handling, reading input and output, and in general anything extra that is not strictly relevant (unless those listed are what you are talking about). The less you have stuff per slide, the better.

    One tip: if you use page numbers in slides, don't use the form "43/300". Instead, just put the current page number or leave it out altogether.

    print "Just Another Perl Adept\n";

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://603718]
[oiskuu]: I'm unfamiliar with android or SELinux. But I believe there is nothing of a kind. Unless you play with capabilities or build your own containers/ namespaces.
[davido]: I am not finding closing STDIN to be an adequate means of making getlogin return undef.
[Corion]: Maybe doing a double-fork (daemonizing) can make go that information away, but maybe not

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (6)
As of 2017-06-23 19:30 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (554 votes). Check out past polls.