in reply to top ten things every Perl hacker should know

Apply grains of salt :)

  1. Perl rocks!
  2. PHP sucks!
  3. Java sucks!
  4. VIM rocks, Emacs sucks! (alternatively: Emacs rocks, VIM sucks! *)
  5. Perl 6 fixes everything
  6. A camel in Perl context can only be used with permission from O'Reilly
  7. There's also onions
  8. Patches welcome!
  9. EFnet #perl is not a help channel
  10. TIMTOWTDI, but only one is the best way

* As long as you pick sides

And, about Perl Monks specifically:

  1. merlyn wrote an article about it
  2. It's tye's fault, but you can blame ar0n
  3. The gods are always right
  4. No, it can't be made faster
  5. Almost everything is set in stone
  6. The sections that we have now are perfect, thank you
  7. If you get more XP than vroom, you get immortality
  8. The assimilation by TPF is forever recent
  9. There is more than one way to scrape PM, and XML may not be XML
  10. Your password is not safe here

Oh well, here's a CPAN list of things you should know:

  1. If you upload to CPAN, you are famous
  2. Modules without recent release are bad
  3. Bogus tests are better than no tests at all
  4. Kwalitee is linked to your karma
  5. Discuss it on the mailing list first
  6. Just don't expect any useful response
  7. After years of development, search.cpan.org now finds DBI if you search for "DBI"!
  8. There is more than one module that almost does what you want
  9. RTFM
  10. CPAN is an archive, but you're supposed delete old stuff anyway
  • 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 VSarkiss (Monsignor) on Mar 17, 2006 at 17:00 UTC
Re^2: top ten things every Perl hacker should know
by johngg (Canon) on Mar 17, 2006 at 14:24 UTC
    Re. salt grains no. 4, they both suck and nedit rocks :-)

    Cheers,

    JohnGG

      BTW, did you try my nedit perl calltips and macros ( just curious)?
        No, but now I know they exist I'll go looking. Is there a URL handy?

        Thanks

        JohnGG

        Update: I've found the call tips on nedit.org but can't see the macros there.