Good points ++.Lack of sensible development environment (no testing/staging area, no version control, etc)
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:
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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||