Good points ++.
Ah, Mr. Spolsky, I don't think I'll ever understand why so many people link to his articles
Just for the record I am not a card carrying Joel fan. I had merely read the article a while back and thought it might have provided some food for thought.
Mind you, his first point wasn't so bad "Just Do It"
Some of his other points weren't so bad either. The main reason I linked to the article was because I remembered that it addressed the issue in the main post of: Lack of sensible development environment (no testing/staging area, no version control, etc) This hadn't been discussed much in the thread (The article mentions bug tracking, specs, cvs). I also think he redeems himself on some of your points in this paragraph. None of these strategies work if you're not really an excellent contributor. If you don't write good code, and lots of it, you're just going to be resented for messing around with bug databases when you "should be" writing code. There's nothing more deadly to your career than having a reputation of being so concerned with process that you don't accomplish anything. -dwiz
-
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.
|
