4 ms·
What? If I'm looking for a job doing x, I'm not going to accept y, and I'm most certainly not going to be playing some game with the employer where I'm tempted
by emilfihlman 5y ago
What? If I'm looking for a job doing x, I'm not going to accept y, and I'm most certainly not going to be playing some game with the employer where I'm tempted by what I want but never given that.
It's the same with testing: it's in huge need but few want to do it, and similar traps are laid there: "come work for us, you can do what you want, but first let's do not what you want".
- denkmoon 5y agoI agree. I am currently in a job where I was brought in under the pretense that while being a developer I would be involved with design work. All my previous jobs, I was involved in design work. That pretense was a lie, I haven't done any architectural design work in over a year now. I simply implement the designs of people that haven't been near a development environment in over 10 years. "This server will talk to that server" is great, until your designer specifies you're going to use passive FTPS and forgets that the particular FTPS server you're talking to has no mechanism to restrict its ephemeral port range, and your customer isn't down for opening ports 1024-65535. "It's just FTP, we'll just open the FTP port". I am miserable because of it. I want a say in what I build, I was promised a say in what I build, and I have no say in what I build.