That princepawn's departure is a failure on the part of the Perl Monks community, not on the part of princepawn
I have to disagree on that one. While a community like perlmonks (or any other) does indeed need members to serve as devil's advocate, or gadfly's as you call them, that role can certainly be filled in a way that is not offensive or unduly annoying. I think princepawn's situation is not an indication of a community that can't tolerate dissent but of one that refuses to allow one strident, shouting voice to drown out an ongoing reasoned discussion.
Varying points of view are tolerated, even encouraged, here. What should not be tolerated is allowing any one person to drown out or dominate the conversation by strength of opinion rather than strength of reason. It seems to me that princepawn largely ignored the (reasonable) wishes of his fellow community members and was therefore ostracized.
We surely must have the right, as a community, to have some say in what the standards of discourse amongst us will be.
~monk d4vis
#!/usr/bin/fnord
-
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.
|