In Defense of Developers

I was a QA data analyst for 22 years, looking for database problems so that they could be fixed. My company had a 99.5% accuracy rate on our products, but even then we might have 5,000 errors, so large was our database. Our customers paid thousands of dollars for our products, as well as a monthly update fee, so errors were not tolerated very well. We had a select group that handled these reported issues very efficiently.

In a modern game with thousands, and even hundreds of thousands, of lines of code, it is simply impossible to thoroughly QA that product before release. A team of 100 people could work for 5 years, and not find the bugs that a few million players will find in a couple of days. Developers know this all too well.

We should expect modern huge games to be released with bugs. Yes, there are alpha and beta test runs, etc. and they should be examined by the developers, but even those instances will not find all bugs and glitches, much less exploits. Players, however, will find those mistakes out in a few hours. They always do.

The developers should be sure the game does not crash out frequently, and the main systems function properly. All player contingencies CANNOT be discovered during the QA process. The real test of a development team is how rapidly they prioritize the bugs, and how quickly they eliminate them. That is their duty before release, and is their primary duty after release.

This does not mean a blanket free pass for really buggy games, or games with game/quest breaking bugs, but only a statement about how complex modern game code has become. It is a daunting task to properly code a game using a huge engine.

So, to sum up: QA is very hard, and will be incomplete due to the complexity of modern gaming engines and the massive amount of coding required.

11 Likes

Yea, I think it’s just a fact of life that games released by a small studio (or even medium sized) are going to have lots of bugs for the first few months. Especially when they try to release on multiple platforms at once.

I can be patient. I think sometimes it’s best to discover a game after it’s been out for at least 6 months and they devs have had a chance to fix all the issues. I was excited for this one, but it is currently unplayable on my Windows 7 system and I don’t expect that to be fixed for a while. So I wait or install Windows 10 (ugh), for now I’m waiting.

1 Like

I 100% agree, certain threads of this forum have turned into real hate pits towards the dev’s of this game and while i think its fair to have an opinion like “oh this game has bugs so i dont like it” i think that mentality doesn’t consider the hundreds of hours put into this game to get it to where it is, especially since this game was made by a smaller team from avalanche. But i guess it’s easier to take something personally than take a second to think of why it is the way it is :joy:
either way though, i’m glad someone made a post like this on here.

1 Like

Yup, I’ve been testing three games for a company, reporting bugs by logging into their database, with all information they need (co-ordinates, screen dumps, type, repeatable and so on) while specifying the severity of it (from critical to aesthetic) and the list keeps growing. The focus always was on the big bugs and then working down to the bottom.

The games have been published when deemed stable from the big bugs, but even then dozens of tester might have missed something, even with us focusing on that. Sometimes told to check for only certain things, sometimes told to play it normally… It was an insane process with thousands of bugs. While I am not active at the moment, I know the list is still huge for the two games still receiving updates and patches.

So yes, if you want the best experience, wait a while, as you say, @xpdx, at least the big bugs that has been discovered even after release will (hopefully) all been ironed out. Patience is needed, no company wish to release broken things as word of mouth is indeed a thing.

1 Like