I absolutely understand where you are coming from. My current task is post-hoc unit testing a legacy C++ system w/ 5k line functions and no docs. Obviously I don't want to be doing that. However I am slogging through because I know there is a lot of potential at my company (assuming I survive my current tasking). Additionally this task, as orthogonal to my interests as it may be, is still providing me with valuable experience in problem solving, test writing, and refactoring. I can't imagine what I am learning now won't be useful someday.
So if you don't see any potential in your position after you survive this first task, and you have other options, then I wouldn't blame you for leaving. However if you believe in this company and can see yourself enjoying future tasking then I would bite the bullet, face the task head-on, and try to learn as much as possible.
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 absolutely understand where you are coming from. My current task is post-hoc unit testing a legacy C++ system w/ 5k line functions and no docs. Obviously I don't want to be doing that. However I am slogging through because I know there is a lot of potential at my company (assuming I survive my current tasking). Additionally this task, as orthogonal to my interests as it may be, is still providing me with valuable experience in problem solving, test writing, and refactoring. I can't imagine what I am learning now won't be useful someday.
So if you don't see any potential in your position after you survive this first task, and you have other options, then I wouldn't blame you for leaving. However if you believe in this company and can see yourself enjoying future tasking then I would bite the bullet, face the task head-on, and try to learn as much as possible.