I have spent the first 25 years of my professional career testing something. In the US Navy, I tested component level electronics. I was the guy always asking for a challenge. After that, I took a career change. That's the time computers took off. I got into testing software. At the time, I was working for Garmin. I got on the phone with three up and coming mapping software companies. With my bosses approval (gotta follow the rules) I provided the specifications for our communication protocols and they sent us software. I tested that software for compatibility with our GPS units. For six years I was the lead test engineer for Digital Ally. In that role, I tracked project hours and kept all projects current. I wrote all of the test documentation for all of the products. I performed UAT, regression and life cycle testing for firmware, software, and mobile apps. Round all of this off with a natural curiosity. I enjoy testing code based products over hardware testing as there are, to my mind, infinitely more things to find. A minor change to a function can have major implications elsewhere. Or is it just a timing issue? I'm good at duplicating my results and when I document findings, I also include how repeatable the issue is. I'm a perfectionist who doesn't allow for close enough. I have taken classes in C, VB SQL and HTML. I have done some independent study in C#. All this to say that I am comfortable around code but am not even remotely a programmer. I am able to follow along and have a general idea what is happening and, therefore, what to expect of it. I haven't always been testing. I worked many support roles. From those, I take away a customer view point. I test as a customer. How will Jon Q. Public use this product? That's what really matters.