I have given a lot of advice here I would not give today.
The other case is just as bad. That is, to go back and change the old posts. History is doomed to repeat itself; if you don't leave the posts there, someone else will "discover" the trick and give out the "new advice." Instead, i would reply to the old post, pointing to what has been learnt. Knowing what used to be thought of as good, and what was learnt over time is best for all.
Well, except for people who look so quickly they don't read the rest of the thread. For them, an "override" post of some sort would be better. Strike-through does do that, but doesn't usually look that great and a quick reader may skip the message entirely. There are ways to finagle this idea, but posting a reply seems to be what most people do.
-
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.
|
