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.

YAPC: Days 1 and 2 9 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Everyone works on different projects, so it's hard when people like Schwern and Andy say "just start testing your code!" to know what aspects of your code to start with. Baby steps, training wheels ... that'd be good.

    I have started implementing core tests that every module is expected to call - stuff like 01compile.t, 02import.t, 03constructor.t, and so on. the idea is that every module should be testing pretty much the same thing at the outset. and even if there is no need for an import() test, I ex

  • Good idea. I'll take it to the QA list and we'll figure out something.

  • I think that if we have individual PM groups go and work on modules for Phalanx, it'll help get the people into the groups.
    --

    --
    xoa

    • That's a damn good idea. Having a group 'adopt' a module too might be a good idea too. So there's more focus and people have a smaller goal they can work on than improving the whole thing.

      I often think we should use the power of London.pm for good as well as evil. I should take this to the QA list as well I guess...which I *really* should start reading more often (bad me.)

  • Thanks for the compliment; I'm glad to know my talk wasn't pure naval-gazing on my part. I did feel odd giving a perl talk with virtually no code in it. :-)
    --

    -DA [coder.com]

    • There were a lot of #perlers whining "we already KNOW this" during your talk, which I took as a thumbs-up for the content and a thumbs-down for their ability to read talk descriptions :-)

      --Nat

      • You're neglecting the possibility that they read the description and went to the talk specifically to whine.
      • We stated the "already know this" bit during the Toronto PM meeting that recapped YAPC, but not as a whine. It was just that since Daniel had given the talk to tpm not too long ago, we didn't need to review it in detail for the people who didn't go to YAPC. The fact that a number of us went to the YAPC talk after having heard it before in Toronto could be taken as a thumbs-up for the content too.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.