We have dedicated QA teams, but we also have embedded QA sitting right next to designers and engineers so they can just say "look at my screen". [Why is that important?]

That's a super important thing. And it's something that we really missed in lockdown. Obviously, as everybody moved into that remote situation, we didn't have the ability to just tap a developer on the shoulder and be like, this is a bug. But now that we're back in the office and we're growing the team again, and we have so many embedded positions that are working alongside that, it's super important, not only for those 'look at this bug, this is so broken, can you fix it?' moments, and that on-the-fly 'yes, done, fixed, submitted', getting stuff out faster. But also the relationship and the processes that we carry in, QA have so much more visibility across development. So when people are making these big features or creating new planets, adding new rivers, putting in a volcano, for example, they have people next to them who can say, there are limitations to the way that you can do this. This is what's happening when you spit it out. One of the things that we see with planets quite a lot when they do reworks on planets is the terrain will shift in height and none of the bases will. So you have to have people who are there to go to those bases and know this kind of thing from the history of these kinds of updates, to help development get past those, especially with the turnover that we see, the growth and the turnover that we see in CIG. It's so hard sometimes to maintain developer loyalty to a very specific feature. It just rolls through so many people that we need this kind of point of information. So it's really, really helpful.