[snip] If you're in a team environment, the best advice I've heard is to have the team share accountability. Meaning, if you write a piece of code, you _must_ have a colleague double-check it and sign off on it. Then if a bug is discovered down the road, _both_ of you will be held responsible. This will do two things: [/snip]
In a team environment may I suggest (as John does here) a peer code review? We used to do his on Friday afternoon, everyone knew it was coming and I usually got milk and cookies for the team (you'd be amazed at the response as hockey as it sounds). That ay all of the projects got reviewed, code was scrutinized and everyone could bug out on Friday knowing where they had to go on Monday. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
