We write a lot of Perl code where I work, and we write a lot of OO Perl in the sense that we use bless and call methods on objects and classes a lot. But I'm starting to realize that we are Perl developers writing OO Perl in much the same way as a C programmer writes Perl, if that makes sense. Part of the problem is that almost everyone here comes from a background of functional programming, so there is really no culture of OO principles.

This is to say that I know that it's not an all or nothing decision to use OO techniques, but I feel like, where we are using it, we're not taking full advantage of its capacities. I came to this conclusion while reading through Fowlers Refactoring and as I'm reading through the "Bad Smells in Code" chapter I'm seeing a lot of things that we're doing. This seems to be a good start for looking for ways to improve our abilities with OO principles.

I'd love to hear recommendations on what other resources people have found useful for learning how to better apply OO techniques in Perl. Again, I'm well versed in the technical implementation of objects in Perl and there is certainly a wealth of information on the topic, it's really more the technique that I'd like to improve.

perl -e 'split//,q{john hurl, pest caretaker}and(map{print @_[$_]}(joi
+n(q{},map{sprintf(qq{%010u},$_)}(2**2*307*4993,5*101*641*5261,7*59*79
+*36997,13*17*71*45131,3**2*67*89*167*181))=~/\d{2}/g));'
[download]