This is my take on game development.
-It is possible to make a complete game on your own, but the limits this would impose, when you are doing all the code and all the artwork, makes the prospect of developing these kinds of games uninteresting to me. I never wanted to do everything myself, and know that I can't be good at every aspect of programming and art. One or two talents is about as much as you can ask for.
-"Collaberative" teams do not work. A team needs a leader who assigns work and sets deadlines. Artists are happy when they feel that the team is moving in one direction.
-You need to tell your artists exactly what you want them to make. Avoid the "make something cool and I will throw it in" syndrome. Don't worry about being bossy. Who would you rather work for, someone with a clear idea on what needs to get done, or someone who just says "do what you want"?
-You are responsible for always knowing how the game is developing, and in which direction it is moving. You need a definite plan on how the final product works, looks, and acts. Yes, it can sometimes be maddening to develop one step at a time, and sometimes doing it without proper artwork.
Leading a team to design an engine, and then design a game with that engine is a very difficult task. It's like a mod team, except instead of using a pre-built, pre-tested engine, you are making one up as you go along.
-It is possible to make a complete game on your own, but the limits this would impose, when you are doing all the code and all the artwork, makes the prospect of developing these kinds of games uninteresting to me. I never wanted to do everything myself, and know that I can't be good at every aspect of programming and art. One or two talents is about as much as you can ask for.
-"Collaberative" teams do not work. A team needs a leader who assigns work and sets deadlines. Artists are happy when they feel that the team is moving in one direction.
-You need to tell your artists exactly what you want them to make. Avoid the "make something cool and I will throw it in" syndrome. Don't worry about being bossy. Who would you rather work for, someone with a clear idea on what needs to get done, or someone who just says "do what you want"?
-You are responsible for always knowing how the game is developing, and in which direction it is moving. You need a definite plan on how the final product works, looks, and acts. Yes, it can sometimes be maddening to develop one step at a time, and sometimes doing it without proper artwork.
Leading a team to design an engine, and then design a game with that engine is a very difficult task. It's like a mod team, except instead of using a pre-built, pre-tested engine, you are making one up as you go along.