1. always 'use strict' and 'use warnings' - its been said a million times, but do it. Optionally remove 'use warnings' when moving code to production. If you can argue for or against this, then this tip isn't for you.

2. Use the 'perltidy' program to tidy up your code. You can apt-get it, yum install, etc etc. It tidies up your perl code in seconds, or perhaps someone elses code. Its configurable if you prefer different layouts. Be warned though, running perltidy then checking in to source repos breaks the 'blame' connection with the original author of each line.

3. Learn about the concept of 'context' as soon as possible. Dont ignore it. Context is at the very heart of perl programming - and related to tip 6.

4. Use Perl::Critic (or perlcritic.com while you are still learning). Its a great way to improve your code and coding. Its like having a crowd of perl experts critique your code and provide detailed feedback.

5. Learn how to use 'perldoc' and get in to the habit early of writing pod yourself. Essentially you just type 'perldoc Some::Module' and you get something that looks like a manpage explaining how the module works.

6. Dont use 'length' to test variables. Perl isnt Java :) in Perl, variables can stand alone in the conditional part of a control statement. Just be awair that '0' also counts as false. Oh, avoid warnings in log files by remembering to test that a variable has content before regexing it or sticking it in strings - use your head about this as you dont need to get carried away.

7. Dont have two modules 'use' each other. Ive seen it, i cant imagine how 'perl' is supposed to make sense of such a scenario.

8. Start learning about how to write tests with Test::More and its friends. Use the 'prove' command to run your tests in bulk, and start getting in to the habit of writing testable code.

9. Read perl books! - Check out the O'Reilly series and various other publishers.

10. Understand that there isnt a 'proper' way of 'throwing exceptions' in Perl. There are few ways, two commone ones are the eval-die method which is somewhat Java-ish or the checking of a return value then inspect a variable approach.