It's to the point where I will only hire Perl developers who either have stuff on CPAN or are vouched for by someone who does.
Actually that is one of the best criteria for checking someone's Perl-fu I heard in a long time.
But sadly one must also admit it will only work for those who know about CPAN and for many PHB a shiny certificate with stamps and seals is "easier" to accept: if anything goes wrong you can always point to the certificate and say "I know he trashed our database, but he was certified for the job!"
A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James