
I've had a team of 3 for 6 months now. Sure we havn't done anything productive, but we're together and will start working as soon as I get the engine semi-usable.
Moderator: Talkative People
Literally 14.hurstshifter wrote:Falco, is Peter's girlfriend literally 14 or did you mean that in the sense of her maturity? Either way, that totally sucks.
No, not at all. Those of us who are passionate about the project have been rocking the house in the super secret private development forum on these boards. You'll see.Trask wrote:I had a feeling that the 'team' is down to it's nitty gritty in terms of members
I couldn't possibly agree with that statement more. I also have a never ending bias against "designers." One guy should not dream up the whole game and tell his slaves what to go implement. I call bullshit.vargonian wrote: I also am not a fan of someone who takes a "designer" role on a small team. If you're on a team of 2-3 people and one of them has the exclusive responsibility of being the "designer", you're getting used. I once naively joined a small team consisting of me (programmer), an artist (who was quite good, by the way), and a "designer". While the designer was a nice guy and contributed plenty of ideas and a solid vision, it tore me apart every day to slave for hours on end implementing ideas that I could just as easily have come up with on my own. My bitterness grew every time he demanded a feature that I knew would create difficult technical challenges for me to solve. Why was I slaving away for someone else's ideas? I have a problem with people who overvalue themselves this way; I'm not saying that designers are never needed, but in this case, his contributions were not providing much added value to the team despite the fact that he expected an equal share of any profits.
Same here really from no experience but from other things thate people come up with the ideas but really don't contribute. A "designer" role should be filled in by a whiteboard marker and a earaserGyroVorbis wrote:I couldn't possibly agree with that statement more. I also have a never ending bias against "designers." One guy should not dream up the whole game and tell his slaves what to go implement. I call bullshit.vargonian wrote: I also am not a fan of someone who takes a "designer" role on a small team. If you're on a team of 2-3 people and one of them has the exclusive responsibility of being the "designer", you're getting used. I once naively joined a small team consisting of me (programmer), an artist (who was quite good, by the way), and a "designer". While the designer was a nice guy and contributed plenty of ideas and a solid vision, it tore me apart every day to slave for hours on end implementing ideas that I could just as easily have come up with on my own. My bitterness grew every time he demanded a feature that I knew would create difficult technical challenges for me to solve. Why was I slaving away for someone else's ideas? I have a problem with people who overvalue themselves this way; I'm not saying that designers are never needed, but in this case, his contributions were not providing much added value to the team despite the fact that he expected an equal share of any profits.
Lol, good onethbp wrote: A "designer" role should be filled in by a whiteboard marker and a earaser
You're such a cocktease. :IGyroVorbis wrote:Those of us who are passionate about the project have been rocking the house in the super secret private development forum on these boards. You'll see.
Rofl.Bakkon wrote:You're such a cocktease. :IGyroVorbis wrote:Those of us who are passionate about the project have been rocking the house in the super secret private development forum on these boards. You'll see.
Falco Girgis wrote:It is imperative that I can broadcast my narcissistic commit strings to the Twitter! Tweet Tweet, bitches!
Or, in my case, your science project is your programming project done solo and you're a mega win. WHAT, WHAT!?kamokow wrote:Small teams can be beneficial some times, but they are also stressful, because some team members wont feel like working, or will not actually work for some other reason. Also, some team members will have a different idea of how they want the project to turn out which can cause issues within the team. Also, comparing programming to a science project is not proving a point at all. A science project will take a few weeks, while developing a piece of software will take months, or years (depending on what it is). Kthx.
edit: just read GyroVorbis' post, i didnt see it :-/
Tru dat.Arce wrote: Or, in my case, your science project is your programming project done solo and you're a mega win. WHAT, WHAT!?
Falco Girgis wrote:It is imperative that I can broadcast my narcissistic commit strings to the Twitter! Tweet Tweet, bitches!
Bot Strike: The Thirdjonemartin wrote:I think it's annoying, which is most likely the reaction most Habs fans are going for.
"Annoy the hell out of the opposing team and everyone watching the game on TV. That'll show 'em. We're Habs fans."
Lock all your doors and windows. Hide your children. Where will he strike next?Bakkon wrote:Bot Strike: The Thirdjonemartin wrote:I think it's annoying, which is most likely the reaction most Habs fans are going for.
"Annoy the hell out of the opposing team and everyone watching the game on TV. That'll show 'em. We're Habs fans."