Looking to form a team.

ID:48848
 
Oct 3 2008, 1:49 am
Keywords: byond, development
Requirements.
  • Must not have an ego. Obviously, that's the reason teams are not formed.
  • Must work for free.
  • Must be available during hours convenient for the rest of the team.
  • Pick one:
    • Prepare for the bureaucracy of the waterfall method. You're not getting what you need to progress until we're ready for you.
    • Note that the design could change at a whim. It's all about iteration. Be sure to schedule time to go through everything with the other team members multiple times.
    • Obey the half-finished design that one person set up for the rest of the team. As with many teams of amateur software developers, the fact that the person trying to form the team is the designer can't possibly be a sign of an ego larger than Jupiter.


Pfft.

As of today, I have written 78 columns of Tech Tree. I'm not saying this to brag. I'm saying this so you may have an idea of how many times I have linked to games that you most likely have either not given feedback to or not even bothered to play. No, they're not all perfect. They'll probably never be. I mean, look at the quality assurance team they use. In the mirror.

How can those who can't be bothered to participate in what is both playable and malleable expect to have their games created with the help of others? If you don't have any interest in another person's ideas, why should others join up around you? Your ego?




PS: I've mentioned this before, but I think that too many people try to form a staff when all they need are smaller works for hire. Developers don't need artist and programmer positions. They need art and code! The work should be divided into libraries which are small enough that people will be willing and able to complete them (with a healthy amount of comments).
Oct 3 2008, 6:08 am
Must not have an ego. Failed.
Must work for free. Failed.
Must be available during hours convenient for the rest of the team. Failed.
Pick one: Note that the design could change at a whim. It's all about iteration. Be sure to schedule time to go through everything with the other team members multiple times. -> You decide.

Do I qualify? =)
Oct 3 2008, 8:30 am
Must not have an ego.

I don't have much of an ego, and am a pretty laid back person. Unless working with retards or unreasonable people.

Must work for free.

Not much bothered about money. I has job.

Must be available during hours convenient for the rest of the team.

Impossible. Time zones make it hard enough, having a job makes it even harder. Wanting a life makes it impossible.

Pick One:
All suck or something.

I'd work as part of a team, but I not avaliable a lot and I am too unreliable anyway.

Also, from personal experience most teams that try to be "serious" like this end up failing. Arguments break out over silly things, and people get annoyed with each other, and in the end nothing is achieved.
The most successful team I have ever seen was the total opposite of this. There was no leader, they were not serious, nor was anyone at any point pressured in anyway. People contributed what they could when they could, and if they couldn't that was fine. (and those that didn't were not recognized as part of the team)
It might not be the best method of getting work done, but outside of a "I am the boss, and I am paying all of you to work for me" situation it is probably the best method of keeping a team alive.
Oct 3 2008, 11:35 am
Requirements.

* Must not have an ego. Obviously, that's the reason teams are not formed. I think I'm good here; as long as I'm working with people that don't say "kin i haz job?"
* Must work for free. Good.
* Must be available during hours convenient for the rest of the team. Meh; I have weird hours when it comes to these things because of homework!
* Pick one:
o Prepare for the bureaucracy of the waterfall method. You're not getting what you need to progress until we're ready for you. Ok
o Note that the design could change at a whim. It's all about iteration. Be sure to schedule time to go through everything with the other team members multiple times. I've redesigned many things many times. I'm definitely fine with this! (My game, Pokemon Amethyst, and it's sequel have had about 5 different attacks systems, total).
o Obey the half-finished design that one person set up for the rest of the team. As with many teams of amateur software developers, the fact that the person trying to form the team is the designer can't possibly be a sign of an ego larger than Jupiter. I can do that. As long as I understand it, at least!

Overall, I can do a little here and there; I just can't be a major player overall.
Oct 3 2008, 12:34 pm
...I think some of you missed the point. =)

I'm not interested in forming a team. At least, not right now. I might possibly have works for hire in the future, I guess.
Nov 14 2008, 5:59 pm
Are all the spots filled yet? I can be GM 2!