Saturday 6 July 2013

The cardinal skills of indie game development

I often worry that I'm wasting my time procrastinating browsing youtube, wikipedia or facebook, when I should be developing games, or improving the skills that help to develop games.

This post is inspired by these recurring thoughts. Earlier today, travelling on the metro, I wrote down what I think are the four core skills I'll need to be a good one-man game studio:

maths
programming
art
music

I then wrote how strong I thought I was in each area. There is no objective metric here; I just wrote down what I felt about my own abilities in relation to where I want them to be. Assuming a scale out of 10:

maths: 2
programming: 3
art: 3
music: 4

I then wrote today's date to the side of the four figures. For too long, a number of these skills have remained stagnant. I stockpile books and cram online tutorial after online tutorial into unseen favourites folders, never looking inside to see the contents. This post represents a change.

Week by week I'm going to record how many hours I'm putting into each skill. The idea is to compete with myself; so when I'm looking at a report at week's end, those are the figures I'll be aiming to beat in the coming week. After several months of this, collecting the reports together and plotting them out on a graph should reveal a pleasing upward trend.

I'll reasses how strong I am at the four cardinal skills some months down the line.

But what's the use of improving the above skills, if they're not actually employed in the creation of games? There must be a fifth, golden metric. The most important metric: game development itself. It's not something I'll mark out of ten at intervals; that's something I'd rather the players of my games judge. But it is certainly something - indeed, the main thing - I can strive to put more and more hours' work into, so this criteria will be way up there, competing for my hours at the very top.