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.
  • But the not-famous in-the-trenches people often share real world-knowledge, telling attendees "here's what you have to do to make it work" without any of the head-in-the-clouds thinking or theoretical concerns that sometimes the famous people are prone to. (hoping I'm not making myself enemies!)

    Not at all, Nat.

    We theoretical, head-in-the-clouds thinkers already hate you! ;-)

    Seriously though, Nat does have a legitimate mandate to provide some "brand name recognition" -- in order to attract attendee

    • It's also important to bear in mind that there is a vast oversupply of proposals to fill the relatively small number of available slots. I don't know what the actual numbers were this year, but I'd be surprised if there weren't at least five hours of proposals for every available one hour of conference time.

      It's more two to one numerically, but that doesn't take into account the durations: we had a lot more tutorial proposals than we could take.

      mysql> select count(*) from e_sess where e_conf='[23]' a

      • Err. 544:179 is fractionally over 3:1.

        But I'm still surprised contention wasn't higher.
        (Of course, if a quarter of those submissions were for tutorials, then that's 136 proposals for maybe 24 tutorial slots, which is better than 5:1.)
        • Err. 544:179 is fractionally over 3:1.

          Yeah, I was thinking "I could have schedule two more for every one I coudl take", hence 2:1.

          Proposal numbers would have been higher if we'd had been more on the ball with PHP and PostgreSQL CFPs. Both those tracks were unnaturally muted, because we dropped the ball getting the word out. (Bruce from PostgreSQL was mysteriously not on the committee mailing list, etc.) It was like an OSCON gypsy curse :( We only managed to get a good lineup for those tracks by dint of much last-minute scrabbling.

          --Nat