Book Review

Code Review best practices

Featured2 Comments

Everyone has there own set of best practices. Here are the few points which I would like to share with you regarding the code review.

The aim of the code review is to build the team spirit, improve the code quality and collaborative learn the best practices.

One feature at a time

Make sure your CRR or commits are based on single feature or story or bug fix. Keeping multiple feature or bug fixes in a single code review request will create more confusion. So keep it simple.

Add members to review

Add everyone from team into in your code review request. At least 2 reviewers should review your code before it has been merged to the remote repository.

Information about what has been changed

Add information about what has been changed in the CRR. Add the related tickets/story/bug link in the CRR (in most of the cases). This will help the peer reviewers to get an insight or information about the task.

Notify the team

Send an Instant message to your team when the CRR request is sent or when the individual completes reviewing a particular request.

If you have any automated system like web hook or slack notification, thats fine. Otherwise, it’s OK to maintain a seperate channel or group to discuss about CRR.

Write it simple and clean

Keep the commit message concise & clear (if it is a bug fix mention it clearly).

When you are reviewing, look into the code and make sure you understand what code does actually; if there is any doubts/clarification needed highlight the code and add comments for clarification.

The aim is to have a readable code, so that remaining team members can also understand.

Be a advisor

If you find the code is difficult to understand or it could be even simpler feel free to suggest the better way to do that.

It’s a good habit to suggest something good instead of just mentioning that particular piece of code can be improved.

Maintain patience

Don’t urge to get your code get reviewed; Give some time to the reviewer and add a gentle reminder if it takes too long.

Be gentle

Stay humble, all these processes are to improve ourselves in a better way.

Code review process is to improve the code quality and build the team spirit in a better way. Collaboratively we can learn more from Code Reviews.

Happy Coding!

2018 Books Reading Wish list

Pandiyan Murugan4 Comments

I’m currently preparing the list of books which needs to read in 2018.

This is just an initial draft, the post will be updated based on books availability and interests soon.

  • The Innovators: How a Group of Hackers, Geniuses and Geeks Created the Digital Revolution – Walter Isaacson

  • The Shallows: What the Internet is Doing to Our Brains – Nicholas Carr

  • The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win – Gene Kim, Kevin Behr, George Spafford

  • Inside Cyber Warfare: Mapping the Cyber Underworld – Jeffrey Carr
  • Computer Science Distilled: Learn the Art of Solving Computational Problems – Wladston Ferreira Filho
  • The 7 Habits of Highly Effective People – Stephen Covey
  • The End of Jobs: Money, Meaning and Freedom Without the 9-to-5 – Taylor Pearson

  • Grit: The power of passion and perseverance – Angela Duckworth

  • The 4-Hour Workweek – Timothy Ferriss

  • What If?: Serious Scientific Answers to Absurd Hypothetical Questions – Randall Munroe

  • Stay Hungry Stay Foolish – Rashmi Bansal

  • The $100 Startup: Reinvent the Way You Make a Living, Do What You Love, and Create a New Future – Chris Guillebeau

  • Rich Dad, Poor Dad – Robert T. Kiyosaki

This is not a checklist or reading challenge list, it’s just a wishlist. Tamizh books details will be added once discussed with my friends 🙂

Please add your favorite books or suggestion list in the comments section.

 

Happy Reading!