APL\360

[wrcooke at wrcooke.net]

> On 01/30/2021 11:50 AM Bill Gunshannon via cctalk <cctalk at classiccmp.org> wrote:
> 
> 
> On 1/29/21 6:08 PM, Sean Conner via cctalk wrote:
> > It was thus said that the Great Will Cooke via cctalk once stated:
> > >
> >>> On 01/29/2021 4:42 PM David Barto via cctalk <cctalk at classiccmp.org> 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?
> They would see you as wasting valuable time fixing non-problems.
> I would not work in a place like that. Worse sti8ll is when you
> work in a place point out logic errors that result in bad answers
> that, obviously, don't get flagged by the compiler and nobody wants
> to hear it.
> 
> bill

That happened too, with similar results.  "Don't touch it. You might 'break' it."  "It's already broken."  "But it 'works'"

That code is running maybe 25% of all mid-sized commercial heat pumps in use today.

"A person who never made a mistake never tried anything new." -- Albert Einstein