Comment Usenet (Score 1) 662
1. Use revision control, e.g. Subversion.
2. Use a formal bug-tracking system. At the very least, numbered text files full of issue descriptions.
3. Start spending some time in the relevant Usenet groups for the languages and technologies you'll be using. This will expose you to the gamut of good and bad practices, let you hear multiple sides to every argument, and put you in a position to make up your own mind about what conventions you care to follow.
