VBGamer

>It usually seems the best coder will be doing all the work, and the others sit and >prety much do nothing... Well thats bad resource management obviously ;). It should NEVER be "the Best coder gets the most work", but more like, "the Best Coder gets the most complex work", and it's filtered down through the ranks, giving a mainly equal share to all coders. The way it should work, is the project leader creates a TODO List, and a basic coding structure and framework (i.e split into classes for easy integration) and then assigns these tasks to the coders, who you provide with the Framework so they can test it / integrate it with the frame work. (Your framework will always need to at least be able to initialise your API, open a window, etc so that people can test their coding with it, this is the starting point). When the project leader is laying out the list of things to do, he/she should obviously place the features which require a class/module to have been already written, further down the list. It sounds quite hard, but assuming you have a basic app framework to begin with (which everyone can plug things into, in a modular / Object Oriented way) and your project leader has done a good job of delegating the work, it can flow quite easily. Remember the key to this, is the ability for someone to just send you their class, which you (and everyone else in the team) can just add to the project and use it straight away, without having to modify 15 different Modules just to get it to work. That spells disaster =) HTH Adam Sysop