So, you have played Satisfactory for thousands of hours. How does playing it for QA purposes differ from playing it casually? Like some people can see a QA role at a game company and be like, "Oh, I love this game. I can play this game for hundreds, thousands of hours. I can do this job." But what does what does QA testing a game, especially a game like Satisfactory, which is so huge, mean? Like actually, how do you approach that? Well, I mean, if I have to explain my job to my nephew, I probably go with that that hey, and I just play at work. >> So, it is just that good. >> But yeah, but if I if I would have to explain it to some grownup person, I'd probably say that yeah, it is still playing the game. >> Mhm. but with some context like with some goal purpose questions, and also chopping the game in into like function functionalities and and and, game mechanics and then trying to test them in isolation. >> Um >> so it's it's still a lot different. I mean- I think when when it comes to, game testing or QA testing u you do a lot more with, playing the game but as you progress in your QA career when you become senior Q the the >> focus shifts towards making, test cases and then you know having like a structure and then doing different kinds of testing like performance and and, memory memory capture and stuff and know those kind of stuff. So it becomes more technical >> and you only like the the amount of hours that you put in just to play the game actually reduces. >> Mhm. >> So yeah.