Porter's World

Becoming A Game Developer

There’s a lot of work needed in order to become a game developer. People often feel that if they have an artist who can animate, and a programmer who knows the language, that they’ve got a team ready to produce quality  games. In reality, those skills are just the tip of the iceberg. A team ready to produce games may be true, but nothing at all says those games are going to be of quality. It takes a lot more than knowing the coding language you’re using, or being an excellent artist; game design itself should be thought of as the third skill required along side programming and art.

I myself excel in my ability in game design. I admittedly lack in programming skills greatly in comparison to what I wish I knew, but I make up for that with my ability to both detect what makes a great game, and how to build one. I find it odd that most teams don’t feel they need a project manager of sorts, someone who understands how games work, what games are good, and what it takes to make them. The team doesn’t necessarily need someone dedicated specifically to this, but one of the artists or preferably programmers should have this skill.

The reason I give this position so much credit, other than the fact that it’s my strong point and I’m proud of it, is that it truly is a concept that I hope more teams embrace. We’ve all come to accept that average art won’t do, if you get higher quality art you’ll see your game value multiply by at least two-three times, if not significantly more. That being the artist’s job, we can look at the programmer now. The programmer is supposed to know what the game needs, then program it. They simply look at a set of instructions and bring the game to life. The last position, again in my opinion usually the secondary skill of the programmer, if not both members, is to know what it takes to make a great game. This however does not mean that the artist cannot have the mind set of a programmer and contain these skills as well, I simply imply that I believe them to be more common among programmers. They need to get over the hype of the game idea and analyze if the game will actually be quality fun; far too many games work as far as functionality, but when it comes to fun they’re simply a bore.

You may be wondering why I suggest that the programmer is the one who holds the magic of the third skill, the answer is simple. The programmer generally knows how the game works from the ground up. They must know how the ideas suggested will co-exist with ideas currently out there, and leave room for ideas to come. That being said, the programmer really shouldn’t be some guy reading an instruction manual on how to build the game, he should be deciding how the game itself is built. This can be done with a firm knowledge of programming, however it’s significantly easier if you possess the skill of understanding how games are built, as well as what makes them fun.

If you’ve already got these skills present within your team, you’re in great condition. If you lack these skills however, I highly suggest you look into partnering with somebody who has experience and understands the above concepts. They may seem like common sense at first, but it’s things like this that make the difference between the average games on the net and the big hits. I’ll continue on these thoughts with follow-up articles elaborating on how you can gain such skills yourself or refine what skills already exist. In the mean time, check out some other useful articles such as, The Importance of Plot and Game Inspiration, to help get yourself prepared for becoming a better game developer.

Part 1 || Part 2 || Part 3