Re^4: Module::Starter (or ::PBP) and Module::Build -- how do I configure the License and Copyright?

[chromatic]

Are you listening to yourself? I mean, really listening to yourself!

If you ... remove all the hyperbole; excessive adjectives, adverbs and superlatives; marketing speak; cutesy and/or tortured analogies; similes and metaphors; unverifiable statistics, bar charts and graphs; and customer testimonials.... Does what's left a) still make sense; b) constitute anything more than just common practice and common sense?

— BrowserUk, Re: Nobody Expects the Agile Imposition (Part II): The Office

Sometimes I think you'd find a way to criticize reading documentation if a handful of other monks started answers with "Have you read the documentation? It says...."

[BrowserUk]

Clever ploy.

Take two unrelated extracts from two unrelated posts, out of context and mix them together.

Add a condemnation of something that might plausibly relate to either (but actually relates to neither). Sounds like I did something wrong, but gives me nothing to respond to.

Pointless and meaningless, but a clever ploy none the less.

If you've a real point to make about either post or thread, I'd love to hear it.

[Anonymous Monk]

Sometimes I think you'd find a way to criticize reading documentation if a handful of other monks started answers with "Have you read the documentation? It says...."

Sometimes I think you're following BrowserUks posts too closely :)

[chromatic]

I happened to have them both open in different tabs at the same time and found the irony intriguing. In one thread, you're supposed to look upon invective and hyperbole with distaste and distrust, and in the other, using Perl::Critic will make you go blind.

[BrowserUk]

Is that really ironic?

• In one, I am the seller. Of an opinion, about the way Perl::Critic tends to be used..

  The program & module suite are sophisticated code, well-implemented. But they are frequently abused because of the over-zealous defaults.

  Newbies and managers rarely read the small print, and if they do, often do not understand the reasoning sufficiently to make their own choices. So they go with the defaults, and the damage is done.

• In the other, I am speaking as proxy for the buyer. Simply counseling caveat emptor.

  By all means, apply my buyer's guidelines to that which I sell. Indeed, I expect it of you.

So applied, the former reduces to: "Do not allow perlcritic to set standards. It is a configurable tool that allows you to police your standards."

And was a reaction to the statement:

It looks like Module::Starter produces a template that falls far short of perlcritic standards,

Paraphrase: Perlcritic doesn't have "standards", unless you "blindly" accept its defaults. Don't!

You see, you do not have to be blind, or go blind, to act blindly.