I take inspiration from all sorts of media, including video games. Every game is designed with the developer’s intent, both in what is explicitly shown and in the underlying, invisible system. I enjoy the experience that the developer has created, but I especially enjoy looking at all the pieces that make the game work. I ask questions like, “Does the game use truly ‘random’ RNG or did the developer tweak it to better suit the player?” “How did such an old game deliver such an amazing experience with such hardware limitations?” “Should I be able to do that, and can it be used to complete the game faster than expected?”The same thought processes helped me as a QA Test Engineer. While I was employed at A-AAccess Online Payments, I had to ensure that new features were working before being integrated into PegasusCRM. At times, I would have to test them creatively. I became skilled at recognizing and cataloging bugs. Even if I was doing something else, I would find a bugs and decide what should be done: Do I diagnose it now, or come back to it later? How do you replicate it? How severe is it? Is it severe enough for immediate attention, or do you just submit it through the ticketing system? Additionally, PegasusCRM has different account types, each with their own permissions and functions. Some of the more complicated bugs involved interaction between two accounts with different permissions, but I was still able to diagnose those bugs and properly document them.During my time at A-AAccess, I learned a lot about how PegasusCRM worked. As such, I would often help in training new coworkers and even some clients in how to use it. Sometimes I would have to teach that person over the phone, without the benefit of seeing their screen. Through patient listening and good instruction, I educated them, teaching them how to do specific tasks with minimal frustration.