My suggestion: Think before you act, gunslinger. Which is maybe a bit (unintentionally) contra Lady Aleena's intentions, but it could link (nb: making some of those quips potential links is a great idea!) to How do I post a question effectively?; IMO many people should heed that advice before they ask anything. There are often posts that (probably) could have been easily solved but are ignored because they are so badly composed, and this could at least occasionally be because someone didn't even stop to consider that the writer != the reader. 'Nother thot: Lack of clarity will get you nowhere.
Something I've found cause to repeat, repeatedly, on other programming forums (but here for the first time) is that 75%+ of the threads I intend to start never appear, because in the course of composing them, I think, "Well if I was reading this the first thing I would suggest is you try _______", and low and behold I solve my own problem.
These lil' ideational hint links could be used with those clever fortune cookie phrases that appear over the search bar too (currently mine is: "laziness, impatience, and hubris").
-
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.
|
