Aran
04-15-2002, 08:39 PM
Here's a little note to all of you new people:
if you encounter someone that randomly starts talking to you about helping him/her develop a game, don't just jump into it guns blazing without knowing what you are getting into. Don't oblige yourself or make any promises for the first few days. Get your feet wet with the person and make sure that you feel comfortable working with them. You should also ask yourself "does this person know what he/she is doing?" and "does this project have any hope of getting done?". If either of these are answered with a 'no' then you should either move on or be ready to do some major learning and working. It is a definate must to ask the person for a copy of his/her design documentation and an executable (or code) that has what he/she has done so far. If you don't like the person's code and/or the person's design documentation is unoriginal, uninspired, or non-existant (to some extent), in most cases the person doesn't know what they are doing, and should just do a solo project to learn how to develop a game and how to code effectively. On the internet it is very easy to just get up and leave, leaving little to no tracks behind you: keep that in mind.
I've had a very bad experience with a recruitor in the past and i'd like others to not have the misfortune that i had.
if you encounter someone that randomly starts talking to you about helping him/her develop a game, don't just jump into it guns blazing without knowing what you are getting into. Don't oblige yourself or make any promises for the first few days. Get your feet wet with the person and make sure that you feel comfortable working with them. You should also ask yourself "does this person know what he/she is doing?" and "does this project have any hope of getting done?". If either of these are answered with a 'no' then you should either move on or be ready to do some major learning and working. It is a definate must to ask the person for a copy of his/her design documentation and an executable (or code) that has what he/she has done so far. If you don't like the person's code and/or the person's design documentation is unoriginal, uninspired, or non-existant (to some extent), in most cases the person doesn't know what they are doing, and should just do a solo project to learn how to develop a game and how to code effectively. On the internet it is very easy to just get up and leave, leaving little to no tracks behind you: keep that in mind.
I've had a very bad experience with a recruitor in the past and i'd like others to not have the misfortune that i had.