Like any good habit, I’ve settled into a cadence with the CodeIt.Right Rules Explained posts. They’re coming about once per month or so, and each one offers a deep dive into three of CodeIt.Right’s rules. As always, I’ll start by citing my two personal rules about static analysis, along with a brief explanation.
- Never implement a suggested fix without knowing what makes it a fix.
- Never ignore a suggested fix without understanding what makes it a fix.
This isn’t a rhetorical game. I could condense the statements and say “learn the reasoning behind all suggested fixes.” But I say it the way that I do to call your attention to a decision that you face when it comes to static analysis warnings. Every time you encounter a warning, you must either choose to ignore the feedback or to address it. And regardless of which you chose, you should really understand the logic behind the suggestion. Otherwise, how can you possibly make the right call?
In that spirit, I’m going to offer up explanations for yet another three CodeIt.Right rules today.