Fuck test automation, it’s a fucking trap get out of it as soon as you can
lol.
Meanwhile, the org I work at has no test automation, so things that should be trivial require hours of tedious, error-prone, manual testing. Also they break stuff and don’t find out until after it’s merged.
This post has appeared in multiple places. It’s useful , but it ruins the development career potential of people that stick with it, because any subsequent job application just sees “TESTER” and not “DEVELOPER” and bars you from changing specialization.
I’ve known several people who moved from QA and testing to developer roles, but usually as an internal transfer.
Most recruiters and management don’t know shit about fuck when it comes to technical details, so it’s not surprising a lot of them think “Oh the guy who knows how software works and how to handle edge cases? No, we don’t want him”
Or the code you are working on is calling a system that is currently unreliable which you cannot be responsible for.
Fuck test automation, it’s a fucking trap get out of it as soon as you can
lol.
Meanwhile, the org I work at has no test automation, so things that should be trivial require hours of tedious, error-prone, manual testing. Also they break stuff and don’t find out until after it’s merged.
This post has appeared in multiple places. It’s useful , but it ruins the development career potential of people that stick with it, because any subsequent job application just sees “TESTER” and not “DEVELOPER” and bars you from changing specialization.
I’ve known several people who moved from QA and testing to developer roles, but usually as an internal transfer.
Most recruiters and management don’t know shit about fuck when it comes to technical details, so it’s not surprising a lot of them think “Oh the guy who knows how software works and how to handle edge cases? No, we don’t want him”