|laziness, impatience, and hubris|
toolic's scratchpadby toolic (Chancellor)
|on Jun 19, 2007 at 18:04 UTC||Need Help??|
perlcritic ..... jul 2012, takes me to undesired: Steffen Schwigon > Benchmark-Perl-Formance-Cargo-0.03 > perlcritic
Perl::Critic ... jul 2012, takes me to desired: Jeffrey Ryan Thalhammer > Perl-Critic-1.117 > Perl::Critic
restore pm node from cache. for example: http://corion.net/perlmonks/910681.xml
(no longer) broken:
For japhy: nevermind... I found your email address.
CPAN module URL, ex. Acme::Tools
http://perldoc.perl.org/functions/state.html /me wonders if reaching 1000 writeups mean he needs to get a life ... outside the Monastery, that is
Re Answer: How do I completely remove an element from an array?: This code generates 2 warnings with use warnings;
Here is some cleaner code:
node id 777777 was created during the 7th hour of the 7th day of the 7th month by a user with 77 in his name... that's a lot of sevens
Just say No to Perl one-liners
Perl Worst Practices
Whenever I see someone asking for a Perl one-liner, the 1st 3 questions that pop into my mind are: Why?, WHY?, and WHY?!?!?!?
I'll admit, they are great for golfing and obfuscations.
How (Not) To Answer A Question
some of that advice applies verbatim here too
WORK IN PROGRESS
compiled from observing good behavior of other monks
be gentle, helpful
if you can't resist chastizing, at least be witty show some effort. When replying to a question, most commonly in SoPW, privide helpful information. Refrain from unimaginative, worthless answers such as:
link to docs other nodes, webpages...
Read carefully through the Original Posting.
If you answer a question hours after it is asked, read carefully through the other replies and try to build upon the repsones of others, rather than repeating nearly identical answers. provide more details, more links, alternate solutions
refrain from publicly embarrassing
use proper English grammar, not web shortcuts "u", "ur", etc.
If you have time, run your own code before posting. Otherwise, mention that the code is untested.
Always provide a link when advising the questioner to RTFM or STFW. Show by example that you have made the effort.
It just dawned on me that PerlMonks are kinda "fuzzy" (this, of course requires elaboration...)
When posed a somewhat obscurely specified problem, the monks generate several distinct, reasonable solutions. Hooray for the monks!
Assume the best
Provide answers at a level of detail which is proprotional to the OP's question. For example, if there is little detail, provide a generic answer, perhaps with a link to an approriate document.