What I like the most is it's challenging and a learning experience. Remember your working along side with the programmer - so what he/she takes on whether it's converting to something different for faster performance, or new functionality using newer technology, your the one whose testing it. What can be stressful is QA gets it last. So although you know testing should never be a shortcut, there's never enough time to thoroughly test, or the QA environment can never match production. I suggest taking classes that relate to the QA work you do. If you don't do QA work takes classes on SQA, black box, whitebox, or even google QA. There's lots of information on the internet at your fingertips.