I was typed as "ENFP". Through those letters, I learned that I have typical patterns of what I lean towards, and I found understanding my stress reactions typical for the type particularly useful over the years in learning to work better with others. I also learned that a "typical tester" would be just opposite, and have tried to keep that in mind when assuming testers should be like me - they typically are not. I also later learned that in strong voices of exploratory testing, there's others who are typed same as me.
My first thought on noticing the session at the conference was that this is again the same old stuff. But right after that came the realization a friend of mine gave me, that is turning into a bit of a mantra now.
The software industry doubles every five years. It means that half of us have less than five years of experience.What's same old and obvious to me, might be something we've stopped talking all in all in the field amongst those who have been around a little longer.
Myers-Briggs is kind of complicated, and I recall reading five books on the topic on my journey back then. I've used a simplification of similar ideas by Lloyd Roden that groups testers into four categories. As I went googling for the reference, I came to realize this is from 1999 and as valid today as it ever was.
Lloyd looks at the then popular writings about personality types, and finds four tester profiles he names Pragmatist, Analyst, Facilitator and Pioneer. Within these, I'm a pioneer. I went to dig out the summary slides I've done when reading the article while being a researcher.
I recognize myself from what the Pioneer is said to like/dislike, as well as can identify with the list of things a pioneer is good at:
- Be good at exploratory testing / bug-hunting / error guessing
- Be good at challenging and improving things to make things more efficient and effective
- Enjoy GUI-type of testing / lateral testing
- Have good ideas
- Be good at brainstorming ideas on what to test
- Share ideas about different ways to approach testing
- Identify and take necessary risks when required
- Have creative ideas on how to test to find more bugs