If you’ve worked with Visual Studio for any length of time, you’ve probably noticed an inverse relationship between convenience and performance. Visual Studio is powerful on its own. And it gets a whole lot more powerful once you start adding plugins. But sometime between that clean Visual Studio install and your 20th helpful plugin, a…
In what has become roughly a monthly affair, I’ll do another CodeIt.Right Rules Explained post today. This marks the ninth such post and roughly nine months of the series. In a now-familiar refrain, I’ll start off by citing my two personal rules about static analysis followed by a brief explanation. Never implement a suggested fix…
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…
Today, I’ll do another installment of the CodeIt.Right Rules, Explained series. This is post number seven in the 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…
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….
Today, I’ll do another installment of the CodeIt.Right Rules, Explained series. This is post number five in the series. And, as always, I’ll start off by citing my two personal rules about static analysis guidance, along with the explanation for them. Never implement a suggested fix without knowing what makes it a fix. Never ignore…
“You never concatenate strings. Instead, always use a StringBuilder.” I feel pretty confident that any C# developer that has ever worked in a group has heard this admonition at least once. This represents one of those bits of developer wisdom that the world expects you to just memorize. Over the course of your career, these…
Today, I’ll do another installment of the CodeIt.Right Rules, Explained series. I have now made four such posts in this series. And, as always, I’ll start off by citing my two personal rules about static analysis guidance. Never implement a suggested fix without knowing what makes it a fix. Never ignore a suggested fix without…
In what has become a series of posts, I have been explaining some CodeIt.Right rules in depth. As with the last post in the series, I’ll start off by citing two rules that I, personally, follow when it comes to static code analysis. Never implement a suggested fix without knowing what makes it a fix….
A little while back, I started a post series explaining some of the CodeIt.Right rules. I led into the post with a narrative, which I won’t retell. But I will reiterate the two rules that I follow when it comes to static analysis tooling. Never implement a suggested fix without knowing what makes it a…
