BlaisePascal is not alone. I have very few days where I
use all of my votes. My voting is based solely on my own
interests. In many cases, that corresponds with the larger
group. I actually posted once (and got severely beaten for
it) that I'd like to be able to view reputation on posts. I
understand the design decision, since it might lead to
bandwagon voting, but it does help if you can see whether a
post is considered worthy by your peers/higher-ups.
footpad, I was impressed by your ability to justify
yourself in that "fight", btw. In this case, I'm with you,
as in I don't understand what fully makes a good node good
and a bad node bad. I had a negative vote on some code I
posted in craft, even though it was on-topic, and completely
non-flammable. Further, I had only posted it for the benefit
of an entirely different conversation. <shrug> I
just figure that it's only fair of me to vote ++ on those
that make me feel ++. I've probably only cast 2% of my total
votes with a --. It seems that's a general consensus with
the other monks (in the site name sense, not in rank) since
it is probably only important to downvote if it really
deserves the punishment.
ALL HAIL BRAK!!!
-
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.
|
