it''s your first team work and then you have such a big team??

i''m working at my first team project right now and we are 2(sometimes 3 because our sound guy isn''t really a member of the team and he doesn''t want to be 2)

me for coding and a friend for graphics...and it works wonderful.

i also prefer being the only programmer in a team, because nobody (excapt me) understands my code ... ok, i dont use many comments or something like this cause it''t MY code. i gotta understand it, nobody else

it''s your first team work and then you have such a big team??

i''m working at my first team project right now and we are 2(sometimes 3 because our sound guy isn''t really a member of the team and he doesn''t want to be 2)

me for coding and a friend for graphics...and it works wonderful.

i also prefer being the only programmer in a team, because nobody (excapt me) understands my code ... ok, i dont use many comments or something like this cause it''t MY code. i gotta understand it, nobody else

Well, it's my second team. I have worked before with a team of 7 members, and it sucked.
But I've learned to make MY programs, so others could understand it too.
You don't need commas, and explaines, all you have to do, is to code nice a tidy
Oh and try to keep some track of what you are doing, because if you do others will understand it too, and it will help a lot.
In real life you and i will both probably be programming in teams, so it's never too early to start learning

Besides, i need all these people, because it is a big project for me.
It is describet better, if you click HERE

Thanks for the post anyway (all 3 of them )
Robert

---

"Find the path, follow the Master... Follow the master, understand the master... Overcome the master !"

[edited by - Dark_Guy on January 27, 2003 5:17:03 PM]

First you need to get your team in same place and in the right frame of mind. Tempt them with booze and a free meal.

Split the project into small chunks and allocate the easy chunks to your newbie programmers, this will give them confidence and saves you having write it all.

MOST IMPORTANT. write down in detail your interface between chunks. Include data structures, function calls. Make sure they all have copy. If you have reformat the loaded map data, then you may well have written the loader for yourself.

I covered this subject at university, but I cant remember more than that.

SwishCheeseHead

Why are you wasting time creating your own engine? Use someone else''s that has already been created and tested extensively and save yourself a huge headache. On top of the engine you still have to make your actual program, a nice UI, and (from the description of your project) a ton of content.