With the rise of low-code and no-code solutions, I've been thinking about the problem they are trying to solve.
This lead me to think wider about ...
For further actions, you may consider blocking this person and/or reporting abuse
Thought proking article Benjamin. It makes me wonder what the next level for testers would look like. This sounds like one kind where a hyper-empowered QA Engineer can assemble a realistic scenario. Of course, I value people that can achieve a high-quality testing process cobbled together without requiring my whole budget. This might be a tough question but where do you see a QA Engineer adding value in an enterprise given this maximalist view of testing?
Us humble QA Engineers often have to manage being a lot of things to a lot of people.
If we are lucky, we are well supported, respected and don't need to wear all of these hats at the same time.
The larger the organisation and the bigger the teams. The more opportunity there is to specialise and add value doing fewer things well.
But there is great power in small teams. I work in a squad as the sole QA Engineer with 6 Developers, a solutions architect, a DevOps engineer and a product owner. I don't do all the things all the time, and I get the opportunity to pair with others in the team to work together to achieve our goal of delivering high quality solutions.
Like I said, making software is a team sport.
Benjamin and Alan, could you both clarify "maximalist description describes pretty much an end to end or system integration test." and "next level for testers would look like."
I did not view this as end-to-end testing but rather integration testing at all layers.
Alan you've introduced a concept of testing levels, I don't think this article established a leveling system but could be wrong.
I read into it. I work on Kubernetes infrastructure things now and problems I would have highlighted do not exist anymore. There are more different emergent problems and I wonder if people are aware that the skills in this kind of role might change dramatically in the next few years.
I tend to find some problems I think have been solved by the industry, reoccurring. What I mean is, there are lots of solved problems that are unsolved for teams and companies that are not at the same level of maturity.
This isn't a bad thing as such, sometimes solving the be same problems again we come up with better and better solutions.
Well now I'm curious, what you feel is solved and what are new challenges. I have some thoughts on the subject of Kubernetes, but would like to know where you are going with it?