Can I be a game designer and a programmer at the same time?

Started by
10 comments, last by Gamer Gamester 12 years, 8 months ago
Hi,

so I was watching some of the GDC vault presentations and in one of them (can't remember which one) about game design, the lecturer said something along the lines: "As game designer you have to come up with ideas that are as crazy as possible, the programmers will tell you what is feasible and what is not early enough.". This got me thinking, because I as a hobbyist am usually the whole "design team", the designer, the programmer and the artist. The moment I start developing a game Idea I also think about the feasibility. Do I have experience with the required technology? Will this work out from a performance perspective? Am I able to produce the required art so it at least looks/sounds ok? So very often if I try to stay realistic with my Ideas I end up being this guy. In the worst case I might end up missing an opportunity to make something unique only because I fell into the trap that the programmer in me tells me: "something like that hasn't been done before and there is possibly a performance/complexity/whatever reason for it".

So is being a programmer something that holds you back as a game designer? Or is it a good thing for "us amateurs" since it makes it more likely that we are actually end up making the game?
Advertisement

1. Can I be a game designer and a programmer at the same time?
2. is being a programmer something that holds you back as a game designer?

1. Yes, of course. Especially if you're doing a game all by yourself, then you must do both functions.
2. No.

-- Tom Sloper -- sloperama.com


Hi,

so I was watching some of the GDC vault presentations and in one of them (can't remember which one) about game design, the lecturer said something along the lines: "As game designer you have to come up with ideas that are as crazy as possible, the programmers will tell you what is feasible and what is not early enough.". This got me thinking, because I as a hobbyist am usually the whole "design team", the designer, the programmer and the artist. The moment I start developing a game Idea I also think about the feasibility. Do I have experience with the required technology? Will this work out from a performance perspective? Am I able to produce the required art so it at least looks/sounds ok? So very often if I try to stay realistic with my Ideas I end up being this guy. In the worst case I might end up missing an opportunity to make something unique only because I fell into the trap that the programmer in me tells me: "something like that hasn't been done before and there is possibly a performance/complexity/whatever reason for it".

So is being a programmer something that holds you back as a game designer? Or is it a good thing for "us amateurs" since it makes it more likely that we are actually end up making the game?


I hear more often than not that everyone needs to contribute beyond just design in order to get a project done. Whether this entails taking part in the actual creation of the game beyond design I do not know, as I am sure there are other tasks to be handled as well.

This paragraph directed towards larger scale games. I am of the opinion that a game shouldn't be designed by just one person, it should be a collaborated effort between multiple people. For one person to make all of the design decisions on a game without any input from third parties is a very dangerous path to travel. If like minded individuals can get together, know the pros and cons, and come to an understanding of what would work best before giving it a shot, more success would be had. I see too many times that people want to be Lead Designer using their ideas as absolute, but people shouldn't be so narrow minded. Being a designer should be enough. Find a premise to start from, get the people together to brainstorm and flesh out a concept, then continue on with the proper steps towards turning the concept into something more. Using a collaborated effort you may also encounter the possibility of having people that are more experienced in certain areas of the design, thus providing more knowledge to the overall design, helping it come together from the start.
Do or do not, there is no try. Contribute what you can, and always compete with yourself. You want to know a little about everything, instead of a lot about a little bit. Don't specialize unless you unionize. Oh and the road of game developer is hard and rocky, so don't expect a light weighted trail. If you make it through your life as a game developer, you will become successful in it.
Failure is simply denying the truth and refusing to adapt for success. Failure is synthetic, invented by man to justify his laziness and lack of moral conduct. What truely lies within failure is neither primative or genetic. What failure is at the heart, is man's inability to rise and meet the challenge. Success is natural, only happening when man stops trying to imitate a synthetic or imaginable object. Once man starts acting outside his emotional standpoints, he will stop trying to imitate synthetic or imaginable objects called forth by the replication of his emptiness inside his mind. Man's mind is forever idle and therefore shall call forth through the primitives of such subconscious thoughts and behaviors that Success is unnatural and that failure is natural. Success is simply doing something at man's full natural abilities and power, failure is the inability to act on what man wants, dreams, wishes, invisions, or thinks himself to do. ~ RED (concluded when I was 5 years old looking at the world with wide eyes)

[quote name='japro' timestamp='1312648784' post='4845474']
1. Can I be a game designer and a programmer at the same time?

1. Yes, of course. Especially if you're doing a game all by yourself, then you must do both functions.
[/quote]
Well, obviously, when I make a game on my own and It isn't a complete ripoff of something else, then I have also designed it... I meant more in the abstract sense. Should I be "using" the mindset of a programmer when designing the game. I even tend to reverse the whole process and think about what kind of game I could possibly make given the code building blocks I have lying around my drive.
Depends. You have to separate the roles - programming and design cannot be interlinked too closely. Now, looking at it from a programming perspective it's certainly valid to make a game from the pieces you'll find lying around - hell, as a design experience that could be quite interesting. Just remember to put away all the nitty gritty details of programming when you are designing the game and get back to thinking like a player :-)
"I will personally burn everything I've made to the fucking ground if I think I can catch them in the flames."
~ Gabe
"I don't mean to rush you but you are keeping two civilizations waiting!"
~ Cavil, BSG.
"If it's really important to you that other people follow your True Brace Style, it just indicates you're inexperienced. Go find something productive to do."
[size=2]~ Bregma

"Well, you're not alone.


There's a club for people like that. It's called Everybody and we meet at the bar[size=2].

"

[size=2]~

[size=1]Antheus
If you can program enough to make draft quality games, you can use this to develop yourself as a designer.
Should I be "using" the mindset of a programmer when designing the game.

Of course you shouldn't design anything that you as the game's programmer know you can't do. Don't put a wall between the two parts of your brain.

-- Tom Sloper -- sloperama.com

Programming helps you become a better Game Designer because you understand how things work.
Yes, you can be both. You can even be an artist as well, if you feel like you can commit to developing your skills. Understanding the technical nature and limitations of both programming and art will make you a better designer.

Back in the early Pleistocene, there were arcades full of video games that were designed and programmed by one person. :P
It is pitch black. You are likely to be eaten by a grue.

This topic is closed to new replies.

Advertisement