The ants are my friends,
They're blowing in the wind.
    - Bob Dylan

Sometimes with programming, it is hard to see the cargo from the cult. With book learning, you are often encouraged to learn by example, where hopefully the examples are good. Though, over time, you tend to forget why you do certain things, but are reluctant to stop doing them.

Initially I found using objects in Perl 5 scary, because early on, the examples were quite lengthy and convoluted, with little explanation provided as to why so much code was required. Sure, I knew objects, from C++ and even OO-Pascal, but it took 20-30 lines to "bless" an object in the early examples.

So, to make objects, you just had to do what the example said, and hope for the best. Only after much experimentation did I figure out the basic requirements, less all the "extra" material that was functionally useless in the vast majority of cases. Why @EXPORT and a BEGIN{} block were ever used in an OO-example continues to remain a mystery.

Also, what is today quite necessary may tomorrow seem like cargo cult programming. For example, if you need to go out of your way to work around a limitation of the language, after time you may do this subconciously, not even realizing that you do it. Maybe you will be fortunate enough to notice, perhaps when reviewing someone else's code which does it more elegantly, or when someone points it out to you.

Perl seems to be an anomaly among programming languages, as with each release, it seems to take less code to achieve the same task. In a world where programming effort and programming error are proportional to that, this is a Good Thing.