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.

use Perl

All the Perl that's Practical to Extract and Report

YAPC: Days 1 and 2 More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Style Guides for Large Projects (Score:1)

by da (1525) on 2004.06.21 19:23 (#31742) Homepage Journal

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]

Reply to This
- Re:Style Guides for Large Projects (Score:2)
  
  by gnat (29)
  
  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
  - Re:Style Guides for Large Projects (Score:2)
    
    by vsergu (505)
    
    You're neglecting the possibility that they read the description and went to the talk specifically to whine.
  - Re:Style Guides for Large Projects (Score:2)
    
    by jmm (276)
    
    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.

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.