{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by KingOfTheNoobs:
2/1/2014 12:55:02 AM
13
Bungie, Mind Giving Tips to Some Aspiring Game Developers?
Hello. I'm a 16 year old Sophomore who dreams of one day (hopefully very soon) making video games. Know this right now, this is not another one of those "How do I become a game developer cause I don't know how to use the google search" threads. About twenty kids, including myself, that live in my local community have set up something I consider to be quite extraordinary. All of us aspire to become game developers and we have decided to come together to produce games. As of right now most of us are in for the experience, but nudged in the right direction I feel this group has the potential to do some amazing things in the future. Bungie, your advice and guidance could help nudge us in that right direction. At the moment we don't have an official name for the group, but we do refer to it as Much Wow Such Games (inside joke). For now Much Wow Such Games would like some advice specifically on getting started, how to not get ahead of ourselves, and how to manage things properly.
For your consideration,
Evan Henry
MWSG Senior Story Writer (Added in just for you Ghost of Dawn)
UPDATE: We have decided to be called Atrium Studios. A name I quite despise, however 2/3 of the team thought is was the best name out of the three final choices. The choices were Urbane Studios (my personal favorite), Atrium Studios (the one we went with), and All American Sweatshop (don't even ask). I also came up with another name, Afloat Studios. Which one would you guys have chosen?
-
1 ReplyEdited by ectomort: 1/29/2014 11:50:49 PMCoordinating a group of 20 people is going to be challenging. There's too much potential for rivalries, range of motivation/dedication, overlapping roles/skills, conflicting opinions and other distractions. Over time, some of those initial 20 may lose interest and drift away (especially as they realize how much effort it takes to make something cool.) I suggest forming smaller groups, [i]project teams[/i] (ideally consisting of 2-4 people) who get along, have a common concrete goal, and have a harmonious set of skills. Figure out who wants what role (e.g. game designer, software engineering, media creative, script/dialog, etc.) and build project teams with a mix of the necessary roles. Each project team can periodically share knowledge gained with the larger group (and encourage each other); but leave decision-making for a project team to that team's members. - use github, Google docs, or similar cloud-based services to facilitate collaboration and keep your code and assets accessible to the project team. - start with a humble goal (for instance to build a demo of a certain mechanic) and plan out a schedule. - meet in-person regularly (i.e. weekly) to check each others' progress and stay on the same page. - avoid "feature creep". - design software for automated testing (this will save you hours & hours of frustrating tedium.) Good luck and have fun!
