You're right Eros, the team has to be organized into positions. There has to be someone who manages everything, someone who maintains the official code, etc etc. For a persistant and similar style it is also important that there is organization inside this project. Before we go on big time like Kent has outlined, everyone should know what they have to do and where they better stay outside. Ofcourse, suggestions are allways welcome and this is how a project grows.
Personally I like to stay focused on one or two things and try to avoid jumping from subject ot subject. Imho that is the death of progress so even if it is very tempting to look at the coding you guys do, I stay outside. Because I don't wanna get sidetracked and I don't see myself as a coder inside the gameproject. You guys do that allready very very good.
We should really try to do only one, or maybe two parts. In bigger teams, you don't see someone doing grafix, writing the storyline, changing code and composing music at the same time. That is why I concentrate on the module. After this is basically done, I will work full force on the game parts that I was assigned to.
We should outline the positions and then everyone should apply to a position they like.
What do you think?
Bookmarks