You don't have good practice as long as you need a tool that beats you into submission. You don't have good practice as long as all you have is just habit.

You can train a horse to stamp it's hoofs resembling numbers according to arithmetic questions you speak. Does that make the horse a mathematician?

You have good practice when you can adapt your coding style to your audience - your team, your customers, your module users, your task, the budget. To be a good orator you need to know grammar, rhetoric, fallacies, intonation and the comprehension level of your audience, and attention and applause are your reward.

To put it bluntly:
Perl::Critic is a utterly useless tool on the path to mastery. It is good for training skilled dogs.

Note that I am not speaking of Damian's "Perl Best Practices" Book here.

The only use I can conceive for Perl::Critic is occasional, in the way I use perltidy. You don't write messy code with garbled indentation and messy line breaks and run that code through perltidy after the fact, do you?

If you need Perl::Critic to enforce a coding style, you have a problem that lies elsewhere.

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}