I think you should be a QA developer. So many people avoid testing because it is executed as a repetitive task. And automation is just a massive maintenance nightmare.
But all of that is nonsense. A good developer will script out the repetitive tasks. They remove unneeded dependencies that cause the majority of "flaky" tests.
Being a QA developer means your solution is no longer a long list of feature requests, it is a solution to solve your problems, not someone else's.
And you get to learn so much. How the frontend works, how the backend works. And you can influence the design, but if you are not sure how to tackle some specifics, there is a developer there to show you the way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think you should be a QA developer. So many people avoid testing because it is executed as a repetitive task. And automation is just a massive maintenance nightmare.
But all of that is nonsense. A good developer will script out the repetitive tasks. They remove unneeded dependencies that cause the majority of "flaky" tests.
Being a QA developer means your solution is no longer a long list of feature requests, it is a solution to solve your problems, not someone else's.
And you get to learn so much. How the frontend works, how the backend works. And you can influence the design, but if you are not sure how to tackle some specifics, there is a developer there to show you the way.