Nice to see people standing up for their beliefs even when it could hurt them.
Story time :)
I remember when I was first starting out as a programmer. At QE (always occurred on a weekend) a slew of financial reports were created and printed for review the following Monday then I think used for summaries for Wall Street to look at.
A high level finance manager came to me and asked if the report could be changed, not knowing what he was asking I said sure. After a long discussion turned out he wanted the numbers on the report changed and re-printed. I said it was possible but the numbers would be all wrong.
So he said "do it". I went to my manager and told them what he wanted, then I refused to do it. I said I would quit first because I did not want the SEC to come after me. Luckily they all supported me and the finance manager was told to "FO".
Yes. You never threaten to resign. You conditionally promise to resign.
I had to make this conditional promise once, back in the nineties, as a junior person in a related industry. Because in the dot-com era developers like me were often simultaneously a babe-in-arms on a professional career level and also the only person who knew how to do the work that was being sold. I decided that if it came to it, I would not be the person having a hard time in court. The client understood better than my bosses and they changed the product. Took them a few minutes at most, but I have reason to believe that my decision made some ripples.
Nowadays I don’t let those issues surprise me: I believe in establishing specific ethical standards at the beginning of projects, because if you don’t do that, you don’t have a basis to robustly point to actions that put them at risk.
jmclnx · · focus · HN ↗
Story time :)
I remember when I was first starting out as a programmer. At QE (always occurred on a weekend) a slew of financial reports were created and printed for review the following Monday then I think used for summaries for Wall Street to look at.
A high level finance manager came to me and asked if the report could be changed, not knowing what he was asking I said sure. After a long discussion turned out he wanted the numbers on the report changed and re-printed. I said it was possible but the numbers would be all wrong.
So he said "do it". I went to my manager and told them what he wanted, then I refused to do it. I said I would quit first because I did not want the SEC to come after me. Luckily they all supported me and the finance manager was told to "FO".
FWIW, that company is long gone.
dofm · · focus · HN ↗
I had to make this conditional promise once, back in the nineties, as a junior person in a related industry. Because in the dot-com era developers like me were often simultaneously a babe-in-arms on a professional career level and also the only person who knew how to do the work that was being sold. I decided that if it came to it, I would not be the person having a hard time in court. The client understood better than my bosses and they changed the product. Took them a few minutes at most, but I have reason to believe that my decision made some ripples.
Nowadays I don’t let those issues surprise me: I believe in establishing specific ethical standards at the beginning of projects, because if you don’t do that, you don’t have a basis to robustly point to actions that put them at risk.