How To Make Your Code Reviewer Like You
By: El Akioui Zouhaire
Tags: Software Testing, Coding, Software Development, Programming, Software Engineering

Photo by heylagostechie on Unsplash

When we talk about code reviews, we focus on the reviewer.

But the developer who writes the code is just as important to the review as the person who reads it.

This article talks about the best books, which show the best practices for participating in a code review when you’re the author.

You’re going to be so good at sending out your code for review that your reviewer will like you.

The Clean Code

Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees.

Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

This book’s biggest strength is that it includes tons of code examples, including some long and in-depth ones.

Instead of just listing rules or principles of clean code, many of the chapters go through these code examples and iteratively improve them.

This book is a must-read for every professional software developer, how wants to pass the code review easily.

Strongly recommended!

Best Kept Secrets of Peer Code Review

Ten practical Essays from industry experts giving specific techniques for effective peer code review.

This book is nice and short; it provides actionable and useful tips for code review.

Highly recommended !

Learning Gerrit Code Review

Learning Gerrit Code Review is a practical guide that provides you with step-by-step instructions for the installation, configuration, and use of Gerrit code review.

Learning Gerrit Code Review is a practical guide that provides you with step-by-step instructions for the installation, configuration, and use of Gerrit code review.

Using this book speeds up your adoption of Gerrit through the use of a unique, consolidated set of recipes ready to be used for LDAP authentication and to integrate Gerrit with Jenkins and GitHub.

Very practical and concise book that guides you through the basic principles of code review and set up of Gerrit.

The pragmatic Programmer

This book will teach not about codes, sometimes you can read but the main idea is to be a better programmer and think better, crack the problems, think about algorithm by yourself.

Its divided in some topics inside some subjects. You can read by look or follow cover to the end.

This book does not have a specific language or a ‘recipe’ to follow, actually it will open your mind to think better.

I think this book is a must for every programmer.

Conclusion

As you participate in code reviews, look for patterns that stall progress or waste effort.

The more you value your reviewer’s time, the more reviewer generates high-quality feedbacks.

If you require them to untangle your code or police simple mistakes, you both suffer.

Emotions run hot when critiquing someone else’s work, But be conscious of pitfalls that could make your reviewer feel attacked or disrespected.

Bonus:

The working environment of an average programmer entails sitting around a desk for long hours surrounded by gadgets.

The reality here is that, there is a huge possibility of programmers developing certain health conditions and computer related injuries.

From my personal experience, I am suffering sometimes from back pain, caused by long hours sitting in front of my computer, sometime with a wrong position.

I recommend a Posture Corrector to regain proper posture which can help to prevent the onset of back, neck and shoulder pain. The Posture Corrector helps provide alignment while sitting, standing, lying down or during your other daily activities.