++ for all that fellow monks said above in favor of Source code control, Regression tests and Group ownership of code.
I would add two more items to consider:
a Bug tracking system and Peer code reviews.
With all these in place, your average bug's life history goes like this:
- identify and report
- describe how to reproduce and provide a test script that demonstrates it
- diagnose and propose a fix
- implement and test the fix
- run other regression tests
- ask a peer to review your change, explain him/her the problem and how you solved it, and show the tests
- submit the change into the source code control system
- mark the bug as done with
Our game writing good sofware. More often than not our peers help us and we help them. Those few who don't - well, they are missing the best part.
Rudif
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.