[Idea]Newb Team
[Idea]Newb Team
Well, This is all just an idea at the moment because I'm working on my personal project at the moment. I was thinking of starting a small team to develop games, not like a team of skilled people. I'm actually gonna find people with basic skills - but still some skills. I think it would be good for a group of new game developers to be all at the same level trying to be creative and explore ideas together. I'm not a great programmer when it comes to games, but I do have a good enough experience to learn it.
I am NOT doing any recruiting of any sort whatsoever right now, I just want an honest opinion. Do you or do you not think it would be a good idea to start a team like this?
--
Remember the team isn't to make amazing games, its to build our way up so someday we will have the knowledge to do so
--
I am NOT doing any recruiting of any sort whatsoever right now, I just want an honest opinion. Do you or do you not think it would be a good idea to start a team like this?
--
Remember the team isn't to make amazing games, its to build our way up so someday we will have the knowledge to do so
--
Well one of the goals is to keep everyone learning the same stuff, if you don't have much modelling or programming skill. Theres virtually no point to be in a group thats bent on learning those 2 bases. A story writer is nice and all but if the team works together they can do it as well. Overall if the group ever winds up ending after I make it, they will be allowed to use anything we create as a group and as well they should have the knowledge to use it all quite well.
In my opinion, working at 2 on the same piece of code without physical contact is very hard. You need to be very rigorous while distributing tasks and be skilled into designing thoses tasks. You will need something like svn or git which is also a difficulty.
I've been coding with people in front of me and through the internet, the first option is definitely easier.
If one is coding when the other one is modeling then that's fine ( you can switch positions every month).
I've been coding with people in front of me and through the internet, the first option is definitely easier.
If one is coding when the other one is modeling then that's fine ( you can switch positions every month).
Re: [Idea]Newb Team
Yeah, only if it's a total
you probably won't get anything done in a convenient way. I think at least one member of a team should know a little bit about design and implementation.mager wrote:Newb Team
Never take advice from someone who likes to give advice, so take my advice and don't take it.
Well, that's reinventing the wheel and there is really no glory in doing so. You should always try to learn as much as you can from more experienced people (this includes books etc) and by the time you've reached a certain skill level you can still go your "own path". The major difference: by then you actually know what you are doing.
Never take advice from someone who likes to give advice, so take my advice and don't take it.
Some people learn better on their own. I've never had a single person teach me something when it comes to programming, and I've progressed quite well. I'm not saying go blindly into something, I'm saying a team of new people to learn, of course we will ask those more skilled than us for help when we need it. But if we don't need it then chances are the more experienced person will end up doing most of the work.
-
- Posts: 226
- Joined: Fri Aug 22, 2008 8:50 pm
- Contact:
I am also in a team and we are going to make the next MEGAPROJECT. The thing started out as a few noobs decided to make a real cool game that would beat anything commerical with ease.
Well, the projekt is going on for a few years, can't say we made that much of progress with anything, but hell yea I learned much! Take irrlicht for example thanks megaproject!
I also learned to lead discussions, organize tasks, advanced 3d modeling, glsl and many other things, not perfect but a team is a cool opportunity to learn.
Yes, the project did not (yet ) turn out like expected but I don't care, I cannot by far say I didn't accomplish anything.
And for small games, I think it would basically the same just a bit smaller or short lived per project.
The one ultimate tip from me: Stick together, do _not_ quit because someone angered you or something (we had alot of these, but the core team is still together).
The more blue-eyed you enter the ring, the more you learn. Often the hard way, but you will gain much.
Also, in our megaproject we have too less people for anything, that is why everyone was/is forced to learn alot on their own. Can't say how it is with smaller games but it is definitly worth a try.
greetings
[Edit] No, Magnon is not my megaproject
Well, the projekt is going on for a few years, can't say we made that much of progress with anything, but hell yea I learned much! Take irrlicht for example thanks megaproject!
I also learned to lead discussions, organize tasks, advanced 3d modeling, glsl and many other things, not perfect but a team is a cool opportunity to learn.
Yes, the project did not (yet ) turn out like expected but I don't care, I cannot by far say I didn't accomplish anything.
And for small games, I think it would basically the same just a bit smaller or short lived per project.
The one ultimate tip from me: Stick together, do _not_ quit because someone angered you or something (we had alot of these, but the core team is still together).
The more blue-eyed you enter the ring, the more you learn. Often the hard way, but you will gain much.
Also, in our megaproject we have too less people for anything, that is why everyone was/is forced to learn alot on their own. Can't say how it is with smaller games but it is definitly worth a try.
greetings
[Edit] No, Magnon is not my megaproject
-
- Posts: 194
- Joined: Thu Mar 18, 2010 3:31 am
- Contact:
I think it's a good idea.
When you are new to game creation, you can easily be discouraged or lose focus.
But when working on a team, especially toward a specific goal you can not only learn a lot, but sometimes even accomplish a lot as well.
When you are new to game creation, you can easily be discouraged or lose focus.
But when working on a team, especially toward a specific goal you can not only learn a lot, but sometimes even accomplish a lot as well.
LazerBlade
When your mind is racing, make sure it's not racing in a circle.
3d game engine: http://sites.google.com/site/lazerbladegames/home/ray3d
lazerBlade blog: http://lazerbladegames.blogspot.com/
When your mind is racing, make sure it's not racing in a circle.
3d game engine: http://sites.google.com/site/lazerbladegames/home/ray3d
lazerBlade blog: http://lazerbladegames.blogspot.com/
buy books. you'll learn like insanely fast. those subtle but important details were written in books, which normally wouldnt be found in free tutorial.
My company: http://www.kloena.com
My blog: http://www.zhieng.com
My co-working space: http://www.deskspace.info
My blog: http://www.zhieng.com
My co-working space: http://www.deskspace.info
-
- Posts: 115
- Joined: Mon May 17, 2010 7:42 am
yeah. some books are a wasting of time.. you have to ask to other people for rights books or online tutorials. The best way to learn is to find immediatly what you need. And this not always appens.
I think a good team have members specialized in different part of the engine. Someone with the SL, some one withe the GUI , some one with 3d modelling ecc.
But there are some very difficult task when working on group.
How organize the work? How to subdive game classes for easy programming and good source distribution into source files.
At the start all programmers must receive general guidelines to attempt for easy integration with others' works.
I have my own project right now. but i'm interested on entering a team . (at the start i looked for Planeshift, but Crystal Space is very strange as engine and i abandoned it). Irrlicht seems the best chance for enter a team. I have a lot to learn and i'm always happy to learn new things.
I think a good team have members specialized in different part of the engine. Someone with the SL, some one withe the GUI , some one with 3d modelling ecc.
But there are some very difficult task when working on group.
How organize the work? How to subdive game classes for easy programming and good source distribution into source files.
At the start all programmers must receive general guidelines to attempt for easy integration with others' works.
I have my own project right now. but i'm interested on entering a team . (at the start i looked for Planeshift, but Crystal Space is very strange as engine and i abandoned it). Irrlicht seems the best chance for enter a team. I have a lot to learn and i'm always happy to learn new things.