Do you know how to laser in on the smelliest code?
30/07/2019 9:02 AM by
Rather than randomly browsing for dodgy code, use Visual Studio's Code Metrics feature to identify "Hot Spots" that require investigation.
- Figure: The bad was is to browse the code
- Figure: Run Code Metrics in Visual Studio
- 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.
- Figure: Find out who the devs are by using CodeLens and start a conversation
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.
Do you feel this rule needs an update?