IMHO Slide 29 is much better now. I see you expanded that chapter with a code outline (or I forgot that it was there). Looks good, second best solution (best solution would have been... a picture ;-). Be careful not to dwell too long on these slides, because for programmers this might be obvious as soon as they know the purpose of the function, for non-programmers these are hieroglyphes.

Btw. I asked one of the best lecturers here at the university whether my advice about the pictures was correct and he said: A picture every 4 or 5 slides is enough and the pictures must be directly connected to the slide otherwise the listeners minds will wander off.

But if you loathe to throw those pictures out now (or you think my advice makes no sense), leave them in. This is then version A of your lecturer-test. Afterwards you can ask some of the listeners if they had trouble concentrating. Next time you give this presentation, show version B with fewer and more relevant pictures. Naturally that is comparing apples to oranges. You have a different audience and there are other factors like time of day and how good you present and the sample is pretty small. But on the third lecture you have an example A/B test you can talk about ;-)

In reply to Re^5: Please review my OSCON presentation by jethro
in thread Please review my OSCON presentation by tilly

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.