Yes, that is true. (Nice reference, btw. 1st Corinthians is one of the better Epistles, in my opinion.) But, I think acknowledgement that it cuts both ways is necessary. When you are part of a team, you have to be willing to work within the team in order to make the team work. Otherwise, it's nothing but a disparate group of individuals each going their own way. While that works for massive groups, it doesn't work for tightly focused groups that need to produce a cohesive product. Diplomacy, the art of getting along, is all about compromise.
I'm not saying that everyone should submit to the Collective. I'm saying that you can't have rabid individualism and still expect to produce a good product.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
-
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.
|
