Il rapporto tra game designer e programmatori è come quello tra presidente e congresso USA


Il gamedev sul rapporto tra designer e programmatori:

“The theoretical relationship between a gameplay programmer and a designer tends to be similar to the relationship between the American president and congress. On paper, congress writes and passes bills, then the president may veto/deny any bill that congress sends to his desk. Similarly, design is usually free to come up with any ideas they want, but the programmer who actually has to write the code to make those designs a reality may veto the design if it isn’t feasible (e.g. it kills performance, uses up too many resources, takes too much engineering time, etc.). If that veto happens, the design needs to be reworked until it is feasible (or scrapped).”

“In reality, the relationship is more collaborative and less absolute. No designer wants their ideas constantly denied, no programmer has the ability to unilaterally veto each designs without a good reason for it, and no producer wants to waste development time. So what actually happens is that designers come up with ideas and programmers help massage those ideas to make them a reality. Sometimes the programmer will have suggestions as to how to make it work. Sometimes the designer needs a better understanding of what kind of technical constraints the feature is under. Neither role really has absolute power over each other, but a good relationship between programmers and designers functions as a force multiplier for better overall results.”

Do programmers have any input on features of the…
Anonymous said: Do programmers have any input on features of the game or are they just slaves to what the designers want? Answer: It depends on the programmer and the team. Some teams are very…

Comments are closed.