It happened to me as well - I found hundreds of warnings in the code and, after getting permission to address them, I was fired because 'we would have to recompile the Windows version due to the changes you made'; the source code was reverted to the state before I made the changes. I refuse to have their product on any system that I have involvement with...
From: "cctalk" <[email protected]> To: "cctalk" <[email protected]> Sent: Friday, January 29, 2021 3:08:28 PM Subject: Re: APL\360 It was thus said that the Great Will Cooke via cctalk once stated: > > > On 01/29/2021 4:42 PM David Barto via cctalk <[email protected]> wrote: > > > Whenever I start a new job the first thing I do today is enable -Werror; > > all warnings are errors. And I’ll fix every one. Even when everyone > > claims that “These are not a problem”. Before that existed, I’d do the > > same with lint, and FlexeLint when I could get it. > > That's exactly what I did. I was promptly told I was likely to get fired > for it. WHY? Why would you get fired for fixing warnings? Would it make some manager upstream look bad or something? -spc
