I had no clue what I was doing when I started testing. I was a user (the only user in fact) of a specific piece of software used to create profiles in order to perform electronic transfer of funds (EFT) – this was when companies weren’t doing EFT yet on a regular basis for business, we were going to have an edge over our competition.
I created the profiles of the business and the banks were interacted with and those profiles allowed us to transfer money between those business and those banks.
Whenever the developers made a change to that software, they would send me a link with a log in ID and password and ask me to take a look at the change and let them know if I thought it was working correctly and what thought in general about the changes (quite a few of the changes came from a direct request from me since I was the only user). They would also ask me to go ahead and go through my entire set up process and make sure everything was still functioning as it should.
I was doing UAT, but didn’t know that’s what I was doing. But I got the testing bug and made it my mission to get in the IT group and do this kind of work full-time. That was 20 years ago and I’ve never regretted that decision. My life went in a completely different direction based on that decision to get into the IT department and I really enjoy sharing what I’ve learned as a software tester and business requirements analyst with other people.