I actually always had that. I just made it several slides.

I also disagree on which solution is best. I've seen multiple programmers try to implement that function and mess it up. There are a number of subtle requirements you have to get right, and I don't think there is any clearer presentation of how to get them right than to show code. I'm not concerned about the common case being wrong. I'm concerned about the production hook going missing, programmers doing the random assignment as $person_id % 2, and other similar mistakes.

I'm leaving the pictures in. I've asked a number of people for feedback, and the consensus of most of them is that the current pictures work well. While I agree that they can be a distraction for someone who is getting lost, I have points where people can resynchronize. And the talk has multiple audiences within any organization, I expect people to lose interest when I'm presenting about stuff they are not interested in. I'd like them to remain somewhat entertained, and then I'd like to get their attention when we move on to a section they care about.

In reply to Re^6: Please review my OSCON presentation by tilly
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.