modules

When I started working on our current project(I’ll wait until James thinks its a good idea to announce it to say what specifically it is). I was thinking let’s start on the most visible part first. Thinking that if there was something to show off it’d be helpful in gaining support.

Minor problem with this outlook is that backend type things are more of my forte, whilst graphics are a weak point. Still I wanted something to be able to show people so i trudged along getting frustrated.

The point of having something to show isn’t to have something visual though, its to have visible progress. A change in tack led me to work on the database first and come up with a way to showing the work I had done so far there. A chart of game flow and a command line prompt worked much better to both show progress and maintain motivation then my crude user interfaced hooked up to a non-responsive system could ever be.

What have I learned from this? In the future focus on the backend with the minimum amount of interface needed to be able to show what you’ve done. Even if the dummy interface isn’t going to make it into the game it can use the same hooks you will use later for the real interface, and may be how you will look for bugs later anyway.

About Anthony Thomas


I am a Georgia Tech Alum living in Philadelphia. I am a software engineer by trade and am trying to start a game company in my free time.

  • RSS
  • Google Buzz
  • Twitter
  • Facebook
  • StumbleUpon