Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Ok, we all know and love the Perl Best Practices book. I wanted to say it before going on.

For the last 10 years I've been the lead developer of a large-scale web application written from scratch in Perl with more than 500,000 sloc according to David Wheeler's sloccount. Thanks Dave.

Recently I started with a new exciting job. And I met people there who do "whatever PBP says". And maybe this is because of their little or no experience and they just want to do "the right thing".

I mean, it's written in the book too, you should take these as best practices. You can agree or not. Of course, they are not meant as religion dogmas. If you have been programming for years, most of the book should be just natural for you.

And what I see instead is that many developers take those exactly as commandments, even if they go completely against the current codebase and guidelines. Just makes no sense.

Also, about Perl::Critic. It's ok and nice, but what's the point of polluting your code with ## no critics here and there? Probably would be better to write your own Perl::Critic::Policy then.

"So, what?"

Nothing special. If any of you had the same experiences, just drop me a note sharing your thoughts. Thank you, fellow monks.


In reply to Perl best practices fanatism by cosimo

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (10)
As of 2024-03-28 12:06 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found