Well, we should consider that the title of the article was "Ten Essential Development Practices", not "Perl Best Practices". ;-)
From what I've seen and heard from the book, it goes into a much more detailed discussion about practices that are more specific to Perl, such as the (ab)use of subroutine prototypes, conventions for passing and using subroutine parameters, how to represent objects in Perl, etc.
I find it interesting that so few of these points are Perl-specific.
It's interesting you mention that. The original set of ten I had planned
to use were much more Perl-centric (so much so that we wouldn't have called them "Essential Development Practices", but rather "Essential Perl Coding Practices"):
Always use strict and use warnings.
Use grammatical templates when forming identifiers.
Use lexical variables, not package variables.
Label every loop that is exited explicitly, and every next,
Don't use bareword filehandles; use indirect filehandles.
In a subroutine, always unpack @_ first, using a hash of named arguments if
there are more than three parameters.
Always return via an explicit return.
Always use the /x ,/m , and /s flags, and the
\A and \z anchors.
Use capturing parentheses in regexes only when deliberately capturing, then give the captured substrings proper names.
Never make variables part of a module's interface.
But as I started extracting these guidelines from the book, I realized
that they relied on the reader understanding and accepting other,
earlier guidelines, which in turn relied on other guidelines, etc. etc.
The book is deliberately put together that way, so that the
recommendations work harmoniously together and form a coherent approach
to Perl programming. Unfortunately that made it hard to isolate just ten
of the Perl-specific guidelines and still have them make sense.
That said, if you want to get a better sense of the (great majority of)
Perl-specific advice in the book, take a look at the beta
chapter we have online.
Things like "write tests first", "use revision control", and "no premature optimization" are almost universal recommendations...
...that people universally don't follow. Hence we thought these ten, though not especially Perlish, would still be a valuable reminder. ;-)
Your article is so great I declared it mandatory reading for our developers and interns :) There's only one point I'd discuss, it's the "always use exceptions" rule. Exceptions suffer exceptions :), for instance for programs that mustn't die whatever happens (daemons, GUI tools for complex jobs, etc).
And concerning the 8th perl coding practice ( Always use the /x ,/m , and /s flags, and the \A and \z anchors.): could you explain it a bit?