What caught my eye in the first couple of lines was this: "fixing compiler error messages".
Which is an excellent description of the actively harmful behaviour my quote was about.
"Fixing" compiler warnings gives your brain the same quick high that a heroin fix will - and is
just as useful. There simply is no fix for a compiler warning.
_Code_ may be buggy or have poor style. Code can be fixed. Compiler warnings are just that:
warnings. They may be valid, they may be invalid and they may point to something much more
interesting in near vicinity. But the strange idea that warnings can be fixed in any shape or
form is plain wrong.
And mechanically going through the compiler output, randomly changing code until miraculously
all warnings disappear is far too common a mispractice to treat it with lenience.
DO NOT FIX WARNINGS!