|Think about Loose Coupling|
Re^5: Modern Perl and the Future of Perlby shmem (Canon)
|on Dec 21, 2007 at 11:39 UTC||Need Help??|
The use of Perl::Critic is fundamentally wrong.
Developing good, then best practices is a good thing; agreeing upon naming conventions and code style also is, nobody denies that, and BrowserUk certainly doesn't.
Good coding practices aren't if imposed and applied after the fact.
Good coding practices are a programmer's attitude towards the job at hand, and this attitude will not develop under any imposition of rules whatsoever, but by understanding them and internalizing them. Best practices are such only in practice, when you are coding.
Once this attitude is fully shaped there's no point in using Perl::Critic, since you know what you do, and why, at every step.
Perl::Critic alienates what has to be a programmer's internal state into a technical instrument, which is wrong. As it is applied after the fact, it is a tool for imposition, which is a hindrance to really developing good practices.