Len

>What I've tended to do in the past (especially for new projects) is to use a set of guidelines of (best ?) practices that should be applied to the particular project. Ideally, all coding/documentation/etc will adhere to these guidelines, but if the programmer finds it necessary to go against the guidelines & can justify to me (& the rest of the team - I have occassionally been known to be democratic) why the guidelines should not be used, then I will accept it.

Having individual guidelines for each project is a bit much, isn't it?

Surely it doesn't effect the outcome of the project if a developer has to change their practices on each new project? Unless you are talking about the look and feel of things like the UI.

Kev