I just enjoy what works, in a particular application.   (And all applications are different.)   It so happens that I like to use things which help me put “all of the relevant code” into one place, and to “hide” things so that the compiler will detect situations where another piece of code (which I never would have found, among hundreds of source-code modules that I didn’t write) might interfere with another, or have a dependency on it, or introduce unwanted side-effects upon it.

Now, the Perl language is weak in that regard ... because of the legacy design of the language and because Moo/Moose are really “just puddings” that have been subsequently grafted onto it.   But that can’t be helped and I’ll take what I can get.   Gladly.

I suppose that I “lack dogma” because, most of the time, I am dealing with troubled, legacy systems which I did not write and for which the original programmers are long-gone.   I’m trying to make improvements to a system that is chock-full of design problems which caused the original team to split the coop.   OOP techniques work well for me, then.   I am often trying to consolidate maybe-hundreds of redundant, sometimes not-quite identical, pieces of code that are scattered all over Casablanca, and to put them into just one place.