so, if they're not .NET Generics, why did you capitalize 'generic' in your question? Hmmmm?
Answering the question, various methods of peer code review work wonders too, as well as all of Esteemed Leader's suggestions. Plus a few coding standards, and giving new team members sufficient time to absorb your codebase before being required to produce anything. Documentation and orientation are great, but developers just need to sit and read as part of the startup. Documentation works on two levels, as well. - Existing documentation gives a reference - being forced to maintain documentation gives an audit trail for people to see what you've done. If you have to add a page to a wiki describing every class and method you create, duplication is easier for others to see. And of course, the ultimate way, is just to fire those who keep repeating history. :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
