in reply to
Perl best practices fanatism
My shop (a dozen or so Perl developers of various levels of experience) adopted PBP in toto as the project coding standard shortly after it came out, precisely because it meant we didn't have to do any thinking. In this case, thinking costs money. Developing our own coding standards, based on PBP or something else, would have cost thousands, possibly tens of thousands of dollars - that's not what the project sponsor was paying us for. We just bypassed all the meetings, discussions and arguments about coding standards, and got stuck straight in to the actual project work. We use the excellent Perl::Critic in PBP mode to enforce adherence. The results have been excellent.
For my next job, I hope to go somewehere that also adopts PBP as the coding standard. If not, I'll encourage them to adopt it. PBP may not be a perfect standard, but it's a very fine one, and with Perl::Critic it's ridiculously cheap and easy to adopt.
+++ to Damian Conway and Jeffrey Thalhammer for making this possible.