Today, I’ll do another installment of the CodeIt.Right Rules Explained series. This is post number eight in this series. As always, I’ll start off by citing my two personal rules about static analysis, along with an 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 might seem glib. After all, I could just as easily say, “Learn the reasoning behind all suggested fixes.” But I say it the way I do to highlight the decision you face when confronted with static analysis warnings. In all cases, you must actively choose to ignore the feedback or to address it. And for both options, you need to understand the logic behind the suggestion from the warning.
In that spirit, I’m going to offer up explanations for three more CodeIt.Right rules today.