I find you have to do this, but it can damage professional relationships.
Recently I've flat out said no, as gently as I could, to doing some work - porting a software stack to run on Windows.
A customer is asking for an estimate to do it, because a project manager who wouldn't be developing or supporting (or even using) the system likes Windows. The sales manager isn't thrilled with me over it.
So he's asked the team as a whole to estimate it because I wouldn't. The rest of the guys are frontend devs. I don't have a clue, they're in a worse position but for some reason they're all up for putting a number to it so I look like a bit of a !
I'm a contractor, so I can and would just turn down the work, but it's difficult politically.
Recently I've flat out said no, as gently as I could, to doing some work - porting a software stack to run on Windows.
A customer is asking for an estimate to do it, because a project manager who wouldn't be developing or supporting (or even using) the system likes Windows. The sales manager isn't thrilled with me over it.
So he's asked the team as a whole to estimate it because I wouldn't. The rest of the guys are frontend devs. I don't have a clue, they're in a worse position but for some reason they're all up for putting a number to it so I look like a bit of a !
I'm a contractor, so I can and would just turn down the work, but it's difficult politically.