But how are we going to know if what they did is the best practice or the best way to do that. Note that we dont have a senior level or an experience developer to check their code.
You could automate the process using
Perl::Critic, which can be customized to highlight what you deem important.
Another effective method for checking code robustness is to run the code on the various platforms/OS's and versions of Perl you have available to you. For example, here @work, I have 3 versions of Perl (5.8.5/5.8.8/5.10.0) installed on 2 linux variants (32-bit/64-bit).
Perl::Tidy is another handy tool to guide new users on consistent code layout practices.
