Code Smell 42 - Warnings/Strict Mode Off
Compilers and warnings lights are there for help. Don't ignore them.
Enable all warnings.
Enable preconditions and assertions in production.
Most languages have warning levels. We should turn most of them ON.
We should run linters to statically analyse our code for potential problems.
- Fail Fast
If we ignore warnings and the code moves on sooner or later it will fail.
If the software fails later it will be very difficult for us to find the root cause.
Defect will likely be near first warning and far away from the crash.
If we follow the Broken Windows Theory, we should not tolerate any warnings, so a new issue will not pass unnoticed in a sea of tolerated warnings.
One man's crappy software is another man's full time job.
This article is part of the CodeSmell Series.