Secret ingredients to quality software


Do you know how to laser in on the smelliest code?

Last updated by Tiago Araujo on 29 Jul 2019 11:02 pm (almost 2 years ago) See History

Rather than randomly browsing for dodgy code, use Visual Studio's Code Metrics feature to identify "Hot Spots" that require investigation.

lotto balls
Figure: The bad was is to browse the code

VS 11 Code Metrics
Figure: Run Code Metrics in Visual Studio

CodeMetrics 3
Figure: Red dots indicate the code that is hard to maintain. E.g. Save() and LoadCustomer()

Identifying the problem areas is only the start of the process. From here, you should speak to the developers responsible for this dodgy code. There might be good reasons why they haven't invested time on this.

codelens start conversation
Figure: Find out who the devs are by using CodeLens and start a conversation

Tip: To learn how to use Annotate, see Do you know the benefits of Source Control?

Suggestion to Microsoft: allow us to visualize the developers responsible for the bad code (currently and historically) using CodeLens.

Adam CoganAdam Cogan
Damian BradyDamian Brady
Adam StephensenAdam Stephensen

We open source. This page is on GitHub