This post from Farnam St had me thinking about what makes a professional software tester.
Most of us are just amateurs.
Whatâs the difference? Actually, there are many differences:
Amateurs stop when they achieve something. Professionals understand that the initial achievement is just the beginning.
Amateurs have a goal. Professionals have a process.
Amateurs think they are good at everything. Professionals understand their circles of competence.
Amateurs see feedback and coaching as someone criticizing them as a person. Professionals know they have weak spots and seek out thoughtful criticism.
Amateurs value isolated performance. Think about the receiver who catches the ball once on a difficult throw. Professionals value consistency. Can I catch the ball in the same situation 9 times out of 10?
Amateurs give up at the first sign of trouble and assume theyâre failures. Professionals see failure as part of the path to growth and mastery.
Amateurs donât have any idea what improves the odds of achieving good outcomes. Professionals do.
Amateurs show up to practice to have fun. Professionals realize that what happens in practice happens in games.
Amateurs focus on identifying their weaknesses and improving them. Professionals focus on their strengths and on finding people who are strong where they are weak.
Amateurs think knowledge is power. Professionals pass on wisdom and advice.
Amateurs focus on first-level thinking. Professionals focus on second-order thinking.
Amateurs think good outcomes are the result of their brilliance. Professionals understand when good outcomes are the result of luck.
Amateurs focus on the short term. Professionals focus on the long term.
Amateurs focus on tearing other people down. Professionals focus on making everyone better.
Amateurs make decisions in committees so there is no one person responsible if things go wrong. Professionals make decisions as individuals and accept responsibility.
Iâve definitely had this in varying degrees in my career. In the beginning, Iâd come up with an idea for testing and just roll with it. As I got further along in my career I started testing out ideas before actually testing. So Iâd think about âIf I do this, what could be the consequence.â which started to frame the idea(s) for testing better and adjust so that my approach was better informed and potentially stronger because more thought had gone into it.
Iâm not getting far past the âamateurâ vs âprofessionalâ definitions⌠Or more to the point, when I relate these two terms to each other, âamateurâ only means ânot paidâ and âprofessionalâ means âpaid.â
Then I continue, and it keeps referring to âamateurâ things in a negative light. Which means that my unpaid-paid definitions of opposing words wonât work in this context. You can be âamateurâ with my defintion and still be good. This doesnât seem to be the case in the quote.
So I try to figure out what the author meant⌠Can Amateur mean âbeginnerâ and âProfessionalâ mean âexpert?â ⌠No, some of the list refers to mindset which isnât exclusive to experts.
So the list is my mind reverts to âlist of some positive mindsets or behaviors compared to list of some negative mindsets or behaviors.â
I think I can relate to all the above quotes from my time as a software test âprofessionalâ, which to me means âI make my living from software testing and I endeavour to work to a different (subjectively higher *) standard to non-professionalsâ. I refrain from using the term âamateurâ and just state ânon-professionalsâ because the term amateur may have negative connotations, e.g. âbah, look at those folks, theyâre amateursâ, but of course it can be used totally neutrally as well.
In the company I work for, at present we have two folks employed as software testers (Iâm one of them) and due to the pressure we are under, the company is starting to need to involve non-professionals in the software testing process. All the quotes above I can relate to observations I have made in the workplace. I think the key one I observe is this: âAmateurs think they are good at everything. Professionals understand their circles of competence.â
I have struggled somewhat to get management to see the possible drawbacks with the statement âanyone with intelligence and business knowledge can testâ. I say âsure they can âtestâ, but can they âtest-testâ?â I think the crux of this is how we define testing, specifically professional testing. If an accepted definition is âhitting buttons on a keyboardâ, then sure enough, anyone can do that. However, if we want to be more rigorous about which buttons to click, ensure all permutations are covered, robustly capture and report the test outputs and know what to do when something doesnât seem quite right during test execution, etc, etc, then maybe thatâs where the non-professionals are thinking they are good at everything whereas the professional knows otherwise. Itâs the old chestnut of unknown-unknowns, i.e. the non-professional doesnât even know what they donât know! Their misplaced assurance/confidence, which may realistically be blissful ignorance, can result in a bad situation when they sign something off and we get bitten down the line in production.
So I think many of the quotes are relevant and good at explaining the differencesâŚ
*I say âsubjectively higherâ because one key difference for me between the professional and non-professional is their openness (even desire when it can lead to learning) to being wrong.
Iâm with @brian_seg. An âamateurâ is someone who does a thing for the love of it. I think the OP meant to distinguish between people who are âprofessionalâ and people who are âun-professionalâ. âUn-professionalâ is not the same as âamateurâ. Iâve seen plenty of âun-professionalâ people who get paid for what they do (whether they deserve it or not).
And over the years, Iâve applied my professional skills to the things I do as an amateur. Both spheres have, I hope, benefitted from this approach.