Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I agree with your 2-3 minute rule. I'll probably skip over some superficial material in the actual presentation and leave it for further reading in the conference materials. The problem was that at the time of the proposal, I had an outline for about 20 slides, so I selected the 45 minute session. As time went on though, the scope of the actual project grew by leaps and bounds, and surprise -- I had too much to talk about. Then again, I don't have a consistent density of material in each slide, so who knows -- I guess my own personal "make test" will tell me more when I do an actual run through of the talk. I can always hold a BOF session for those who want to know more. :)
    • Slides as OSCON conference material are only any use if you provide them on paper or give a download link, so I wouldn't count on the material being useful if you don't do that. (OSCON doesn't do printed stuff for anything but the tutorial sessions)