Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I stared at Him for a good fifteen seconds. Then I got up and left the room.

Well done. Many people seem willing to sacrifice what they know are absolute minimum standards in order to get the job "finished".

In a previous project I worked on, not just the programmers but also the project management had fallen to this rubber-stamping dark side. In one case people were left out of a code review, since their (expert) comments would presumably slow things down. I've seen more than one review announced out of the blue for a major piece of code (>10K lines) just a few days before it occurred. I think the classic case occurred when a review consisted mainly of people that didn't know the language the code was written in, so I'm sure the review went smoothly.

In reply to Re: On Commenting Out 'use strict;' by bluto
in thread On Commenting Out 'use strict;' by Old_Gray_Bear

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.