Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??


Here's why: You do not put forward any arguments for either the authority or efficacy of the result of compliance with P::C. Nor do you state an single example or any reasoning for your conclusion that P::C improves beginners code.

Wow. You disagree with me, so you downvote me. Thank you for ensuring that I won't get into any future discussions with you.

However, that isn't quite correct. I specifically said that since we started using Perl::Critic with some of the inexperienced guys I work with, their code quality has improved, and the number of mistakes they have made has decreased. That specific experience is why I believe it helps improves beginners code: I have personally seen it happen.

You simply state: "I like; I use it; therefore it must be good."

No, I didn't. I'll thank you for not putting words in my mouth. In fact, I'll help you by directly stating what I mean, in my own words: "I like it. I have personally benefited from it, both through direct use, and from its use by coworkers. For my purposes, it is a good and useful tool."

Pick (almost) any single one of P::C critiques and open up the discussion here to all comers comments; and I'll bet you'll never reach a consensus; without you give a specific example of the critiqued construct or idiom in situ. And even if you get a consensus for that specific usage, it will be only for that specific usage; and probably a contrived one at that.

You are correct in that you will probably never get 100% agreement on, well, pretty much anything related to Perl. Especially when it comes to things like best practices. Hell, getting 100% agreement is almost a violation of Perl's TIMTOWTDI culture. But, that doesn't mean that I don't have personal opinions on best practices. And it doesn't mean that a significant number of people in the community don't have opinions on best practices. And it doesn't mean that my coworkers don't have opinions on best practices.

Can Perl::Critical assist us, at least to some degree, with catching violations of those best practices? Yes. Is Perl::Critic perfect? Absolutely not. Is it useful? To me, absolutely. Do I think it's better to have new users run it, research what it spits out, and learn from it, rather than blindly continue making potential mistakes? Yes.

I think this comes down to a fundamental difference in viewpoint on learning. You seem to imply that Perl::Critic is always bad, and that the only valid way to learn best practices is through code reviews with a presumably experienced Perl coder. I believe that a code review with an experienced Perler is absolutely better than Perl::Critic, but I also believe Perl::Critic is better than nothing (and many people don't have a Perl guru at their beck and call). Finally, I also believe that Perl::Critic use, especially when supervised by an experienced Perl coder, can be a very beneficial tool for learning.

I find it to be (one of many) useful tools. You obviously hate it. Nothing in this discussion is going to change either of our opinions, and I'm not interested in arguing with someone who downvotes first, and argues later. I'm out.

In reply to Re^4: The Most Essential Perl Development Tools Today by topher
in thread The Most Essential Perl Development Tools Today by Tommy

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    [Discipulus]: sure! probably the last chance to choice my holidays, 3 weeks

    How do I use this? | Other CB clients
    Other Users?
    Others pondering the Monastery: (9)
    As of 2018-06-25 18:25 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (128 votes). Check out past polls.