As Developers, we often face a moment of “What is this piece of code precisely doing?” And this is the moment of Code review. There are lots of analytics, passion and hours behind the lines of code. But are all these values ever recognised by the outcome? Yes, they are. Every developer that realises this is definitely on the track to contribute toward quality. Rather than start with coding, analyse the need and perhaps the bigger picture. Once the need is understood, the code can become a paragraph of a story. A story that has an impact and is still a part of a chapter. Once the Code can live and breathe by itself, the storytelling, or the code telling, comes in. The code has to tell the code reviewer what is happening here. And as often, in iterations, code improvement will lead to a better understanding and knowledge sharing amongst the developers. Some clouds will pass by in the real world and challenge the journey. A process that isn’t integrating Code Review, Time which isn’t available, Tools that don’t work or don’t exist to simplify code review, and a question of “Why do we need to spend time on this”. If these clouds can be addressed and handled, the success of managing quality increases for sure.
17 November 2022
More Story Bytes