Ray Warner · QA Pillar Manager, Squadron 42Absolutely. That's what I mean when I say there's got to be a very specific mindset to get into QA and remain good at the job. It's about problem solving. And when I say problem solving, it's not about being presented the problem and finding the solution, it's about finding the problem. And that's very much what you're talking about. It's about seeing a piece of software or seeing a feature or seeing an element of gameplay and thinking to yourself, and our backers are great examples of this, how are people going to come in and ruin this? Because they will. The first thing they want to do is find easier ways to do things or better ways to get things, ways to exploit the code, ways to exploit the gameplay. We have to approach our testing methodologies with this in mind from the very, very get-go.
Phil Webster · QA Pillar Manager, Persistent UniverseRight from the start, like in the kickoff meetings, the amount of times when designers come in and they do the pitch and someone from QA will go, so that could be weaponized by doing A, B and C, right? And their faces drop and they're like, oh, yeah. But that saves time, and it gets that fixed before it even hits the code base. So it's very important.
Rodolfo · Global Director of QAWe actually had one of those today, right? It's very important because sometimes you can have a design that will not work out in the whole universe, and people don't figure it out until it's coded and gets into QA hands. So we actually test it and it's too late, because you have to drop the code and start again. So it's so much better when you can have this interaction in the early stages of the development lifecycle.