Let’s do another installment of the CodeIt.Right Rules Explained series. Today we have post number six in that series, with three more rules. As always, I’ll start off with my two personal rules about static analysis guidance, along with an explanation for them.
- Never implement a suggested fix without knowing what makes it a fix.
- Never ignore a suggested fix without understanding what makes it a fix.
It may seem as though I play rhetorical games here. After all, I could just say, “learn the reasoning behind all suggested fixes.” But I want to underscore the decision you face when confronted with static analysis feedback. In all cases, you must actively choose to ignore the feedback or address it. And for both options, you need to understand the logic behind the suggestions.
In that spirit, I’ll offer up explanations for our three rules without further ado.