Re: top ten things every Perl hacker should know

I think you omit a number of things that are of crucial importance

Know what the Phalanx 100 is, and study it. It is an excellent starting place for finding out what CPAN has to offer.
Know the name of your local CPAN mirror.
Know how to install a CPAN module directly without the assistance of cpan or cpanp.
Know what mailing lists are available, and subscribe to the ones that you think are important or interesting.
Know where the next, nearest Perl Workshop or YAPC will be held.
Know how to file a bug report. Does the author like to receive e-mail or do they mention that they prefer to use Request Tracker? (One prominent author refuses to use rt.cpan.org).
Know how to comment out large slabs of code easily.
Know how and when barewords are interpreted as strings or globs
Know what the indirect calling notation is and why it is deprecated.
Know what lexical filehandles are
Know that a warning in an if statement may well be related to a chained elsif further down in the code.

Goodness! I'd better stop. I'm up to eleven already.

• another intruder with the mooring in the heart of the Perl

Comment on Re: top ten things every Perl hacker should know

Replies are listed 'Best First'.
Re^2: top ten things every Perl hacker should know by holli (Abbot) on Mar 16, 2006 at 21:16 UTC
Know how to comment out large slabs of code easily. Mark the block to be commented. Fire up search and replace in regex mode Search for "^", replace with "#" Of course you need a decent editor. The other way round should be obvious ;). holli, /regexed monk/	[reply]
Re^3: top ten things every Perl hacker should know by xdg (Monsignor) on Mar 16, 2006 at 23:48 UTC
Or better yet, teach the editor to do 1, 2 and 3 (and the inverse) as a macro. And for those without a decent editor wondering what to do, I assume the original reference was about using Pod: `=begin comment # lots of code here =end comment` [download] -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply] [d/l]
Re^3: top ten things every Perl hacker should know by johngg (Canon) on Mar 17, 2006 at 14:09 UTC
At the risk of starting up a whole new discussion, my vote for a decent editor goes to nedit. Cheers, JohnGG	[reply]