QA Is My Hero

Let’s talk about Heroes and Villains for a moment.  I read a post on another blog a few days ago – and I’m sorry, but I can’t remember which blog right now – about the main differences between Heroes and Villains.  Essentially, the thesis was this:  Heroes have to wait for bad things to happen before they can do their thing, but Villains just do their thing.  I happen to agree.  Villains are active, Heroes are reactive.

Let’s apply this to QA and game development, shall we?  Designers are active.  They choose what they want to put into the game.  They choose when.  They choose how things will be implemented.  They just do their thing.  QA, on the other hand, are by necessity reactive.  QA can’t do anything unless something is added or changed.  Then they get to check whatever was added or changed and try to get it corrected (which is their thing).  QA are Heroes, by this analogy.

That’s not to say that Designers are Villains.  I think of Designers more like Mad Scientists who are trying to make the world a better place, but sometimes unintentionally cause harm.  Then the Hero has to come in, stop what they’re doing, then give a heartfelt lecture on unintended consequences.  At least, that’s how it happens in my story.

So remember, Designers, “QA is not the enemy”.  In fact, they are your Hero, even if you don’t know it.


Comments are closed.

%d bloggers like this: