Peer programming is another possibility. If he is with another skilled developer on the team who dies meet quality standards and knows procedure then this has a few benifits:
- With an experienced developer over his shoulder he will learn what is expected of him and see the difference between his code and code that meets expectations
- The other developer can enforce a test first policy: not allowing code to be written until tests have been written for it
- Similarly, the other developer can verify that the code is up to standard before it is checked-in reduicing the nmber of bad check-ins
All of this of course requires the company and developers to be receptive to this process which they may not be.
