What they DON’T tell you about being a game developer

Original Author: Alex Norton

So I’m in an interesting position. Malevolence, while not my first game by a long shot, is my first RELEASED game, and I’ve been lucky enough to have it gather a lot of attention (for an indie title) early on in its creation. From what people tell me, this does not normally happen. Normally, a developer will hit on gold after they’ve tested the waters with a few titles first, or had a hand in other game development, such as working for a AAA company.

Because of this unique perspective of having a relatively successful title (despite not yet being released) on my first ever attempt, I haven’t yet developed the pessimism that often comes with being an experienced indie game developer. This has led me to want to write this new thought piece, which goes into all of the things that they DON’T tell you about being a game developer. If you want the short and sweet version, feel free to skip to the end.

STAGE 1 – DELUSIONS

—————————

Going through university I had the same delusions as most people that I would get my qualifications, build a folio and get a job at a AAA game company. Shortly thereafter, fame and riches would ensue and I would live happily ever after, making games that I love, and having everything right with the world.

I finished university to find that all of my hard work would get me on a “consideration” list for a baseline, entry level QA job which would mostly consist of me being locked in a cubicle for 70+ hours a week doing some of the most repetitve, soul destroying work known to man.

A good example of what it is to be a tester, provided by Penny Arcade.