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…
I’ve heard tell of a social experiment conducted with monkeys. It may or may not be apocryphal, but it illustrates an interesting point. So, here goes. Primates and Conformity A group of monkeys inhabited a large enclosure, which included a platform in the middle, accessible by a ladder. For the experiment, their keepers set a…
Today we released CodeIt.Right v2.2 – new version that adds introduces 23 new rules – Usage and Asynchronous programming best practices – as well as new feature allowing to output analysis results to Visual Studio Error List in addition or instead of CodeIt.Right Violations Report. Here is high level list of new features: Added 12…
