Year in review #2019

Its time to look back and see stats of #EfficientUser website.

👀 50000+ Views

Views is the one of the key factor in the blogging world to show how much our content being helped others or reached the audience. We have received 50,000 + views in this year.

🎅 41000+ Visitors

Visitors are the individual person or session who visited our blog. We have grabbed attention 41,000 + visitors this year.

🔠 5033 Total words

For me, the number of words doesn’t decide the quality of particular post. However, I typed 5033 words to make 16 posts in this year (excluding this post).

👆 1824 No. of clicks

Conversion is the important business model in the marketing. Even though we doesn’t have any product in our blog, user clicked 1824 times to visit other post or linked articles which brings more interaction to website.


Followers are the early adopters in any blogs or product. Thankfully, we have ~563 people to support our blog (including social media, email followers, and so on.)

🔣 315 Avg. words / post

On average, we have 315 words in blog post which published in the year 2019.

🏁 180 Countries

We have got traffic from around ~180 countries. This is huge for an individual blogger I guess. Wow!


Likes are the virtual handshake given by audience to the author. We have got 33 likes in 2019.

📬 16 Total Posts

We made 16 concrete blog post in this 2019.

Quoting: Quantity doesn’t matter Quality does


Comments are the real boost for the content creator. we got 13 comments in this year 2019.

An the Emerging post in 2019 – Technical Debt

😎 1 author

We got 1 author behind all this posts in 2019, that’s me, thanks!

To get latest updates you can follow or subscribe! #peace


Photo by Joshua Chun on Unsplash


Code Review best practices

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!