Jump to content
  • Advertisement
  • entries
  • comments
  • views

How to fix bugs

Sign in to follow this  


Today, I'm a bug-fixin' machine. I spent all morning bringing up all of the games and writing down any bugs that creeped in. Most of the ones I found are related to replacing the bitmap engine. A couple are related to the replaced timer stuff. One I just can't figure out at all :)

Surprisingly, I'm rather enjoying this step. I think it's a bit like editing a novel. After staring at individual pages through a magnifying glass, it's gratifying to step back and look at the entire product as a whole. It's finally coming together, and I can see the finish-line on the horizon.

People seem to have one of two attitudes towards bug-fixing. The first attitude was summed up by one of my former co-workers who became upset whenever I found a bug in his code. He seemed to view bugs as a deficiency in his skills (or his character). He even went so far as to access my computer after hours to cancel an automated stress-test that I was allowing to run over a weekend. I think he cared more about how his coworkers looked upon his coding skills than shipping a bug-free product.

I'm not claiming to be a moral paragon of any kind, but I try to have the second attitude. I really value bug-reports from people, and I try to challenge people to break my code. It's sometimes an ego-blow when someone clobbers something that I thought was perfect, but I know my limits. I know that the stuff I write isn't perfect, and the only way to make it perfect is to let people try to break it.

That being said, here're my rules for working with testers.

  • Be sure to let testers know where the possible trouble-spots are in your program. Let 'em clobber the tough spots.
  • Make a game of it. Challenge your testers to break your code, and gloat when they can't. Allow them to gloat when they've found something.
  • If someone points out something as a "bug", but it's simply that they weren't using a feature properly, you should look very closely at how the feature works. There's a reason they weren't using it correctly --maybe it's not as obvious as you thought.
  • Fix minor stuff like typos immediately. Some people like to bunch 'em up and fix all of the minor stuff at the end, but sometimes fixing a typo leads to unexpected side-effects (like stuff no longer fitting in a dialog-box, requiring you to reformat things).
  • Immortalize your testers in the "about" box. Your product wouldn't be as good as it is without 'em, and they deserve recognition.
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!