I belong to a number of communities for game developers, and one issue that comes up again and again is motivation. I happen to be a firm believer that strict self-discipline is one of the greatest tools you can have for self-motivation. Wait! Don’t run away! I’ve got easy answers as well as hard truths!
This scene looked a lot less appealing when the camera would suddenly spin through 90 degrees,
Despite my belief in self-discipline, I also believe that there are simple things you can do to help build motivation and to help you through the hard times. This week, I’ve been preparing the first beta version of Supreme League of Patriots – Episode 1. Inevitably, as you get closer to releasing anything – alpha, beta or full releases – you start finding more and more bugs and issues. It’s Sod’s second law of coding or something. Bugs can be funny things. Sometimes you can get a huge, crushing bug which spreads damage throughout an entire piece of software, yet it can be relatively easy to fix. On other occasions, you can get a handful of tiny bugs which – on their own – present no great danger, but together form into some complex web of destruction where every bug you fix breaks three others. This – for me, at least – is one of the things which most threatens my natural tranquility.
My desk always has a pen and a memo block on it. You’d be surprised how quickly that pad disappears. Or if we’ve worked together in the past, you probably wouldn’t.
I’ve actually found a pretty good way of handling bugs though. I’ve been using it just over a year – ever since someone gave me a block of yellow post it notes. My desk always contains a pen and a block of post it notes, or a memo block – something along those lines. That’s the first rule. The block/pad never goes anywhere else. Every time you see a bug in your game, you write a quick note on the top sheet and tear it off. Not only if it’s a definite bug. Not only if you know how to reproduce it. Even if you’re fairly sure it was just a trick of the light. Because let’s face it, it never *is* a trick of the light. That bug you pretend you didn’t see will always come back to bite you in the arse two days before a milestone release – at which time you will have no idea why it’s happening or how to reproduce it.
Never throw the notes away until the bug is fixed. If you find a way to reproduce it, add instructions to the note or staple a second note to the first. Don’t just throw another note on the desk, because you’ll lose track of which belongs with which. Don’t tidy the notes. Don’t move the notes. Don’t put the notes inside something. Keep them strewn across your desk where you cannot miss them. The more notes you get, the more motivated you will be to fix them, because your desk isn’t getting any tidier until you do.
Finally, here’s the really good bit. When you fix a bug, take the note, screw it up into a ball and throw it into a wastepaper basket. It’s incredibly cathartic. You can even write notes for bugs you fixed before writing them down if you really feel the need for motivation. Clearing your desk of notes will give you a positive glow, but it’s really the sense of power you get from destroying and jettisoning that little post it note that gives you a warm fuzzy feeling inside. Give it a try, and help boost your motivation a little. If you find it useful, give me a shout on FB or Twitter (see below) and I’ll write more articles on things that help me through the tough days as a developer.
This is what a good week of bug fixing looks like. Lots of dead bugs. Also, caramel eggs. You can never have too many of those.
Follow me on Twitter : http://www.twitter.com/nobullintention
Follow me on Facebook : https://www.facebook.com/SupremeLeagueOfPatriots