Code revision is necessary

You should be wondering, what does code revision means. With my research I have found that there is more that most starting or new coders don’t do, and this is one of the most important.

Also call peer review, it is considered an activity that asures your software quality, so in this way one or mere teammates for the same project so more than one be sure getting to check the code, preferably together, this lead us to the ruber duck methodology which I find very exciting.

The ruber duck debugging is the way to explain a certain part of your code to someone, if you are alone you can explain it to you ruber duck, so you will go one line at the time. Then at the same time you explain it to someone else or even your duck, you are comprehending and checking for mistakes or things to improve.

The main objective of this process is to detect quality problems, although it can be used to reach more goals. Better code quality: improve the readability, maintainability and comprehension. Finding defects: finding performance problems, security vulnerabilities among other flaws. There are many more goals that can be achieved through this process, but the general idea is to create better software and to avoid errors.

The rubber duck is a way to make your review but in a more professional level more methodologies exists to help you out, for example:

• The formal inspection is the traditional method of review. Software developers attend a series of meetings where the code is reviewed line by line. This method has been proven to be very effective in finding defects in the code.
• Regular code review also called control version review, so it records changes into a files or set of files to maintain a history for every changed you have make. You all should know by now that what I am explaining is a sort of git, one of these is github, the one that i personally use, and not necessarily review one line at the time, but you can also implement it.