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.
  • OSCON topics (Score:3, Informative)

    by gnat (29) on 2003.02.10 14:53 (#16854) Journal
    I always ask people "what are you hacking on?" Tim makes a big deal out of tracking the alpha geeks [macdevcenter.com], but the truth is that the interesting stuff that people like you and Matt Sergeant [uwinnipeg.ca] and Leon Brocard [astray.com] are hacking on will be in everyone's face next year. So if you have a project you've been beating on in your spare time ... kick it loose!

    Another approach is a case study: is your company willing to talk about how they used Perl or any other open source system to make millions? Alternatively, if your company creates open source and has a justification for it in the business model, can you talk publicly about it so that other companies can see the light?

    Pick a module you can't live without and convince others how great it is.

    Figure out what you'd have to teach your replacement. If there's a skill (writing test cases, XS hacking, your preferred XML translation system, a particularly cute way of reading email from Perl) that you think applies outside your company, then submit a talk proposal on it. Think: core skills.

    Some topics off the top of my head, not necessarily relevant to you, but which might kick-start others thinking:

    • WxWindows tutorial
    • Inline tutorial
    • vcard or ical talk
    • POE tutorial
    • practical AI
    • top ten things found in code audits
    • top ten things you can do to make your code easier to read
    • analysis of why a particular module or system Got It Right (what makes it well-designed or implemented)
    • template toolkit tricks
    • five critical OO design patterns you've used in the last six months
    • signal handling
    • threading
    • five things everybody does wrong with XML
    • practical talk about the content management system you use (what it does, how you have it set up, how you use it to do the things you want)
    • live coding (build a program or a module in front of the audience). NB, risky!
    • Why You Should .... (tell people what they should be doing)
    • I Saved My Sanity With ... (module/system/methodology/insight here)
    • Guru Session (get together with one or two other experts in your field and take questions for 45 minutes)
    Hope this helps!

    --Nat