Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I actually often edit a node four or five times after I press submit, for the first five to ten minutes. Sometimes it's in response to a CB that says I hosed a link or something. Other times it's just because I came up with a slightly different second take on something.

After I stop twiddling the node, I follow the normal guidelines: no editing of the node, just adding "<hr><b>update:</b> extra text" below if it's minor, or an entire new node if it's in reaction to a reaction.

If you're going to cache the "original" version of a node, I suggest a nominal cooling-off period of at least 15 minutes.

-- Randal L. Schwartz, Perl hacker


In reply to •Re: New "feature" -- view nodes as they were originally posted by merlyn
in thread New "feature" -- view nodes as they were originally posted by blakem

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.