Skip to main content

Testers of past be the IT stars of the future?



Been noticing two a bit conflicting themes lately.

1. Testers getting (or pushed) to be more technical and write test automation code

2. Articles listing future IT core skills as widely non-technical

So whereas many testers are moving to work more on test automation, the vital skills of the future may be such as:
- Creativity
Analytical (critical) thinking 
Activlearning with a growth mindset 
Judgment and decision making
Interpersonal communication skills
- Complex Problem Solving

Which sounds almost like a list of vital skills needed for an exploratory tester. 

So we should perhaps remind the ones starting a testing career or moving away from it, that also these skills are something that can be quite valuable in the future as well.

Maybe even the most valuable.

Comments

  1. First theme is a gut feeling, but to some extent backed by changes in testing and development conference programmes (testing getting more technical, development more soft).

    Second is what I've been noticing in my different feeds, but can be backed up by google search "future skills of IT work" returning stuff like: https://www.engineering.com/JobArticles/ArticleID/16807/4-Cornerstone-Skills-Engineers-Need-for-the-Future-of-Work.aspx and https://www.forbes.com/sites/bernardmarr/2019/04/29/the-10-vital-skills-you-will-need-for-the-future-of-work/

    Or this all could be social media algorithms feeding my confirmation bias. Hard to be sure about anything these days.

    ReplyDelete

Post a Comment

Popular posts from this blog

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? After t

I don't report bugs

I don't report bugs . Bug is such a loaded word that people understand very differently, that instead of using it and explaining what I mean by it I rather just use other words. Like observations, thoughts, surprises, ideas, alternatives, or something similar. (And no I don't use fault, defect, or error either). Bug has also quite a negative connotation. "Reporting a bug" is kind of like telling someone that they've been served. And as we are actually giving away the gift of information, why wrap it in such a nasty package? And maybe more importantly it is very likely that whatever you might have to say is wrong. If not plain wrong, then at least incomplete. So I like to approach the kind of situations with the assumption that I am probably wrong. Cutting off anything that might sound arrogant makes stuff quite a lot easier. Especially after you realise later on that you have been wrong. I leave plenty of observations unreported . I don't want to waste

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.