Perl Monk, Perl Meditation | |
PerlMonks |
Re^4: On being 'critical'by polettix (Vicar) |
on Dec 16, 2006 at 16:38 UTC ( [id://590218]=note: print w/replies, xml ) | Need Help?? |
If the boss asks to be "compliant" with Perl::Critic and PBP, I read this as a requirement to adopt the practices in PBP as coding standards.
Now, each company can have its peculiar coding standards, and TheDamian also warns that those in PBP are to be taken as things to think about, rather than absolute rules by themselves. He tries to explain why he adopts a particular solution, and why it should be considered a best practice, but the decision is up to you. PBP can be taken as a coherent set of coding standards, but they're not the "bible" and any company can set its rules, of course. This actually moves the discussion towards the good and bad of having company coding standards. I think that coding standards promote ease of sharing code across the whole company, preventing anyone from having bad surprises that bite for a long time before being spotted. As an employee/consultant/whatever, one can agree with the company coding standards in the same way as one can agree with its ethic standards, but if one decides to go on she should adhere to them. So, what I was pointing out here is that we're not discussing whether that particular coding standard is good or not, but that adopting those workarounds leads to a shallow compliance, breaking the underlying requirement. Flavio
In Section
Seekers of Perl Wisdom
|
|