You need to be a premium member to use this feature. To access it, you'll have to upgrade your membership.
Become a sharper developer and jumpstart your career.
$0
$
. 00
monthly
For Basic members:
$10
For Premium members:
This article provides a broad overview of the review process for the code written in C# using Visual Studio 2015 and also uncovers best practices for code review.
Abstract This article provides a broad overview of the review process for the code written in C# using Visual Studio 2015 and also uncovers best practices for code review. Code Review is a very important part of any developer’s life. Code review is a technique which allows another developer (not necessarily working in same team or same feature within a team) to go over-n-through your code line-by-line and identify areas for improvement or point out holes. Hence, code review is a process and not a technology. However, there are some developer productivity tools available (mentioned later in this article) which can enable a developer to write good quality code. Disclaimer There are numerous guidelines and best practices software development teams follow and depend on. This article will uncover most of those but it may not cover all the best practices around code review. However, I want to assure you that all the guidelines mentioned below will help any individual to practice and apply good coding principles and perform a quality code review. Is it a must to have my code reviewed by other devs? Well, you must. But it depends on your team’s development methodology and ALM (Application Lifecycle Management) tool settings. There are ways to bypass the code review by simply just not doing it and straight checking-in the code. It’s not recommended though. What if my code is not reviewed? It’s hard to say, but at times and in some cases it might cause serious issues and raise concerns for the whole team. For instance, a condition check is missed, or null is not handled properly or not all error situations are being handled by your exception handling block. Well, these examples might sound very simple and most of the developers do write defensive code and cover such aspects. But what code review can also provide value towards is your “design”, “techniques”, “patterns”, “approach” etc. How to find a code reviewer I have worked in various team settings and work environments. Many times I have been invited to perform a code review for a developer who is not part of my team, or rather, I am not part of their team. But what I admire and appreciate here is the fact that someone reached out to another dev in case their team’s developer is either not available or busy with critical production issues, etc. Such a mindset empowers the team to deliver the best written code. Let’s Begin with Best Practices of Code Review Here, I am going to list out some areas which are critical from a code review perspective. I tried to highlight the core best practices which are a must in any code review. I have seen many times that in a code review developers are more focused to look for code design patterns or some areas in code review,
Summary Above mentioned code review guidelines are light weight, easy to look for and easy to apply techniques with larger impact on any code base. Mostly it has been evident that simple things are either ignored or not cared about. These best practices can be added up with more guidelines or in combination with other techniques as applicable. Happy Coding…
Exploring Design Pattern for Dummies