Perl is rather refreshing in the fact that it has tremendous power without shoving your nose into “and this is the one-and-only ‘right’ way to do it.”   (The essential way that Perl implements all of this stuff ... the bless verb ... always leaves me saying, “that’s it?”)

If possible, look at a bunch of existing object-oriented Perl code.   The CPAN library is a fine place to do that, since you can look at the source-code to any package right there on the web-site.   Just choose packages of recent vintage.   Take a very close look at Moose and its many brethren, and do this very soon.

If you find yourself dealing with a legacy application that is written in OO-Perl, as is often the case, make sure that you continue to do things the same way such things had previously been done, if possible.   Because the language does not impose a single right-way to do almost anything, I think that it is generally most important to stay consistent, and clear.   (“Golf” is a game, not a best-practice ...)

Comments, for example.   They’re still free.   “Tell me what you’re thinking right now.”   Explain to me the clarity of your thoughts.   Even if you are writing for yourself, to yourself, you will find that you do not remember what you wrote when you read it again.   But, I guess, I digress . . .