Code review: 8 step guide

Code review: 8 step guide

Reviewing someone else’s code might sound like a trivial task, but believe me, it’s never easy. If you are going to review someone else’s code, there is a certain level of expectation from you.

If you or your team doesn’t yet have a code review process in place, or you have been asked to perform code review as an outsider, here are the 8 steps that will guide you through the whole process.

SOLID: Single Responsibility Principle – (SRP)

SOLID: Single Responsibility Principle – (SRP)

The principle states that, if there are 2 reasons to change a class, the functionality should ideally be split into 2 separate classes. This is also related to the concepts of coupling and cohesion.

Single Responsibility Principle can be considered as the most important design principle one needs to adhere to, as everything else flows from this, in one way or the other.