[AitchEmArsey]

The other side of this coin is that if you are are forced into actions which you "know" are wrong and just accept it, then maybe the job is already dead for you anyway. By fighting back you are testing a number of stress points, like the conflict-avoidance of your management and the belligerence of the person you know to be "wrong". The important part is having the maturity to understand the consequences of being mistaken yourself, and being able to decide whether the fight is worth having even if it is going to have drastic results. In other words, is this a hill worth dying on?

[geraldwhen]

No hill is worth dying on for a company, unless perhaps its an early stage startup and you're running out of cash.

I have a family to support, and saying "OK" to bad decisions from on high has never threatened my livelihood.

[disambiguation]

> No hill is worth dying on for a company

Wish I got this advice much earlier in my career

Though on the flip side, don't sit and eat shit from your company when you have extremely high value in the fastest growing industry in the world.

[Daishiman]

> I have a family to support, and saying "OK" to bad decisions from on high has never threatened my livelihood.

This doesn't necessarily work out in practice. When bad decisions have consequences many people will look for scapegoats, and blindly following orders can still make you a scapegoat.

[geraldwhen]

In my own past I’ve pointed out issues non-confrontationally. But I smile and go along with it if the feedback is discarded. I’ve seen tens of millions of dollars lost to bad tech decisions. Occasionally someone will mention that I predicted the failure a year or two prior, and I shrug.