Re^2: Strict and warnings: which comes first?

> Neither, those things hurt job security.

hmm ... actually it never occurred to me that secretly deleting strict and warnings before delivering code might be a clever move. xD

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

Comment on Re^2: Strict and warnings: which comes first?

Replies are listed 'Best First'.
Re^3: Strict and warnings: which comes first? by Eily (Monsignor) on Nov 13, 2019 at 16:41 UTC
That's because you get better results by deleting your colleagues.	[reply]
Re^4: Strict and warnings: which comes first? by LanX (Sage) on Nov 13, 2019 at 17:21 UTC
Actually I'm in a complicated migration process to AWS and quite happy that some colleagues are not reachable at the moment. ;-) Not because they are not qualified, but because management is totally underestimating the effects of communication overhead. see The_Mythical_Man-Month Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]