The hardest part in my job these days is thinking commit and PR messages :/
I believe my code and commits and PRs are always self explanatory, the company doesn't agree apparently.

  • 1
    I use commit and PR messages to describe the value or feature added by some code. Don't describe what changes you made in the code, describe how that improves the software.

    Don't say "Modified Log.error method to include a priority parameter", say "Adds priority to error logs". Maybe not the best example, but I think it makes commit messages more succinct and useful. They can see what changes you made by looking at the diff.
  • 0
    Write the app as you would get the marketing department after to recommend label changes ect.
Your Job Suck?
Get a Better Job
Add Comment