Why isn't this just hire 500 more QA people and this gets fixed?
TL;DRJens Lind says the problem came from the 4.8.1 database combined with 4.8.2 data, an environment QA doesn't have, so hiring many more QA people wouldn't have caught it.
In this case, it took the situation of how the database on 4.8.1 was, with the new data from 4.8.2, to create the situation. And that's not something that the QA environment has. So whatever we do, we as a technology group would have to come in and at least give them that. And then if you put your 500 QA on it, then probably one of them would have spawned an Idris. But without that environment, you could put as many as you like on it. No one would ever have discovered this situation. This is just too far removed. And I think that sort of comes back to the large dataset, right? As you have a large dataset, you just can't scale in manpower alone. You need something that scales way beyond that.
I suppose if you just hired 500 QA people, that doesn't mean there's 500 requisite programmers that can all take the stuff and fix it either.
I think that would meet some frustration with their output, and our ability to tackle it would certainly create a separate set of challenges.
Also, what's frustrating with this situation is that we've done multiple patches where this just worked fine.