"We human being, always find a solution, maybe not today, but if you really want to solve a problem, there’s always a way" – Ma Yun @ Stanford, 2013

Five rule of thumb for a backend developer

by Md Imran Hasan Hira
Five rules of thumb for a backend developer, so that your peer can live a happy life.
  1. The name populate_data() doesn’t help much. The first question comes up to mind – What kind of data? So if there is name for your data, use that, instead of just data.
  2. Instead of warning fixed or bug fix, please write at least an oneliner of what warning you fixed.
  3. And then, instead of just fixed the warning, include the actual full error/warning message from stacktrace at the end of commit message.
  4. The names process() / execute() / handle() is ok in case of library/framework methods. But for general purpose, please specify what you are processing/executing/handling. For example process_million_dolar_payment() / execute_superman_command() / handle_http_request() …etc. At least try to use longer if you can. It helps with fewer grep results.
  5. Don’t have any on top of my head now :p


Leave a Reply

Your email address will not be published. Required fields are marked *

Theme by Ali Han | Copyright 2025 Md Imran Hasan Hira | Powered by WordPress