answer:Have you tried peer code review? Every couple of days go through and review all the new code publicly with everyone in the group. Have the person who wrote it explain what they did and then talk about what could have been done better and possibly even how they could have to gotten to the solution more quickly. It can be humbling for everyone involved, but I think it has a lot of benefits. 1) If you know something is going to be reviewed, you’re going to do a better job initially 2) You know you’ll be able to ask questions if you aren’t sure about something, or better yet ask questions before you fall into category 2 or 3 above. 3) Things end up more uniform between coders and since you eventually have to interact with other folk’s work, this makes that process easier 4) Each person gets to develop their skills based on the knowledge of others in the group It’s a time investment but you end up with much better code and programmers who are able to develop their skills rather than keeping the same habits.