I'd go for this as well, but would like to add: "make him need to work with his collegues to accomplish the project". As in this way "code review" is naturally supported by all team members, and it will show clearly the need to stick to coding conventions, modularization and open ones eyes for security issues as the other programmers don't want anyone to plug security holes in the code to which they provided secure scripts/ modules to.
0.02

Have a nice day
All decision is left to your taste