Patch 2.0.5 Issues - WoW Insider

Reader Comments (Page 1 of 1)

1-14-2007 @ 11:49AM

BlizzardHasTerribleQA said...

Wow, you know you're in trouble if a college CS kid is telling you that your code sucks. But welcome to the real world.

While it's highly desirable for companies to fire people for releasing crap, that just does NOT happen. If it did, Blizzard would've had to fire their entire development and QA staff -- this is not the first time they screw stuff up! I think the only other MMORPG company that has screwed up more is SOE but SOE had a few years head start!

For you QA people out there! Get a freaking clue! I can count the number of useful QA people that I've had over my 10+ years in the industry on one hand (and I still would be able to even I lose a couple of fingers!)

Add your comments

Your comments:

Remember me

E-Mail me when someone replies to this comment

Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.

When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.

To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.