Rules Archives - Software Quality Blog

CodeIt.Right Rules Explained, Part 22

February 12, 2019Carlos SchultsNo Comments

Welcome back to the CodeIt.Right Rules Explained series. For those of you who haven’t seen an installment in this series, let’s explain what it’s all about. CodeIt.Right is a tool that performs automated code review for .NET. It checks your code against a set of rules, giving you valuable feedback on its quality. Throughout the series, we’ve been explaining these rules, always three at a time. In every post in this series, we start with the following two rules of thumb: Never implement a suggested fix without knowing what makes it a fix. Never ignore a suggested fix without understanding what makes…

CodeIt.Right Rules Explained, Part 17

June 19, 2018Erik Dietrich1

It’s time for a deep dive into yet another three CodeIt.Right rules. In case you’ve missed it, this continues a post series in which we, well, do a deep dive into the CodeIt.Right Rules. CodeIt.Right is an automated code review tool, making it fall under the broad heading of static analyzers. It checks your source code against a set of rules, both ones that you customize and a set that comes out of the box. In this series, we’re focusing on the latter, since those are the ones that will obviously apply to everyone. Followers of this series will know that I…

5 Ideas for Rules to Add to Your CodeIt.Right Profile

April 24, 2018Erik Dietrich1

A while back, I wrote on the subject of code review horror stories. This was mostly for fun, but it does speak to an important truth. Code reviews can be pretty contentious, unpleasant, and even counterproductive when done wrong. I could spend a bunch of time today talking about how to do them right. But I won’t. Instead, I’ll talk about ideas for how to automate your way around possible points of contention. I’m nothing if not a software developer at heart. Automated Code Review Goes Beyond the Default Rules You might be wondering how one “automates around” contentious code…

CodeIt.Right Rules Explained, Part 14

March 6, 2018Erik Dietrich1

Today, I’m doing another post in the CodeIt.Right Rules Explained series. For anyone who hasn’t seen one of these before, here’s briefly how it works. CodeIt.Right is an automated .NET code review tool, and it has a lot of rules to help you. In the posts in this series, I explain those rules in detail. Whenever I post in this series, I start with my two rules of thumb for static analysis. Never implement a suggested fix without knowing what makes it a fix. Never ignore a suggested fix without understanding what makes it a fix. As always, I’ll explain that…

CodeIt.Right Rules Explained 13 includes

CodeIt.Right Rules Explained, Part 13

January 30, 2018Erik Dietrich1

It’s time for another post in the CodeIt.Right Rules Explained series. If this is the first such post you’ve seen, I’ll explain briefly how it works. CodeIt.Right is an automated code review tool for .NET, and it has a bunch of rules. In these posts, I explain those rules in detail. Whenever I post in this series, I start with my two rules of thumb for static analysis. Never implement a suggested fix without knowing what makes it a fix. Never ignore a suggested fix without understanding what makes it a fix. As always, I’ll explain that I don’t phrase…

CodeIt.Right Rules Explained, Part 12

November 28, 2017Erik Dietrich1

This week, we bring you another post in the CodeIt.Right Rules Explained series. In case this is new for you, with each post in the series, I take you through three CodeIt.Right rules in detail. CodeIt.Right is an automated code review tool, making use of static code analysis. As I always do with these posts, I’ll start with two solid rules of thumb for static analysis. Never implement a suggested fix without knowing what makes it a fix. Never ignore a suggested fix without understanding what makes it a fix. And, as I always do, I’ll explain that I don’t phrase…

CodeIt.Right Rules Explained, Part 11

October 31, 2017Erik DietrichNo Comments

It’s time for another post in the CodeIt.Right Rules Explained series. I daresay it’s becoming a pretty predictable post series, with a pretty predictable cadence. And that’s a good thing! CodeIt.Right offers automated code review, and this series of blog posts gives you a detailed tour of the what and also the why of the code review rules. As has become custom, I’ll start with two solid rules of thumb for static analysis. Never implement a suggested fix without knowing what makes it a fix. Never ignore a suggested fix without understanding what makes it a fix. Every month, I…

CodeIt.Right Rules Explained, Part 10

October 10, 2017Erik Dietrich1

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…

Using CodeIt.Right at Scale on Large Codebases

September 19, 2017Erik DietrichNo Comments

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 noticeable slowdown occurs. The user experience starts to suffer. Of course, this isn’t unique to Visual Studio. It applies to pretty much anything with a plugin ecosystem, such as a WordPress website or your browser. In all of these cases, you have to weigh the…

CodeIt.Right Rules Explained, Part 9

September 12, 2017Erik DietrichNo Comments

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 without knowing what makes it a fix. Never ignore a suggested fix without understanding what makes it a fix. It might seem I’m playing rhetorical games here. After all, I could condense this to say “learn the reasoning behind all suggested fixes.” But I say…