dev-jhon-yo

1. Use descriptive and obvious names.
   • Don't use abbreviations, use full English words. player is better than plr.
   • Name things as directly as possible. wasCalled is better than hasBeenCalled. notify is better than doNotification.
   • Name booleans as if they are yes or no questions. isFirstRun is better than firstRun.
   • Name functions using verb forms: increment is better than plusOne. unzip is better than filesFromZip.
   • Name event handlers to express when they run. onClick is better than click.
   • Put statements and expressions in positive form.
     • isFlying instead of isNotFlying. late intead of notOnTime.
     • Lead with positive conditionals. Avoid if not something then ... else ... end.

• If we only care about the inverse of a variable, turn it into a positive name. missingValue instead of not hasValue.

dev-jhon-yo

{
  "workbench.startupEditor": "newUntitledFile",
  "editor.fontSize": 14,
  "editor.lineHeight": 1.8,
  "javascript.suggest.autoImports": true,
  "javascript.updateImportsOnFileMove.enabled": "always",
  "editor.rulers": [
    80,
    120
  ],

lucianodiisouza

- **100% — FF**
- 99% — FC
- 98% — FA
- 97% — F7
- 96% — F5
- 95% — F2
- 94% — F0
- 93% — ED
- 92% — EB
- 91% — E8

diego3g

{
  "workbench.startupEditor": "newUntitledFile",
  "editor.fontSize": 15,
  "editor.lineHeight": 1.8,
  "javascript.suggest.autoImports": true,
  "javascript.updateImportsOnFileMove.enabled": "always",
  "editor.rulers": [
    80,
    120
  ],

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default

evaera

1. Use descriptive and obvious names.
   • Don't use abbreviations, use full English words. player is better than plr.
   • Name things as directly as possible. wasCalled is better than hasBeenCalled. notify is better than doNotification.
   • Name booleans as if they are yes or no questions. isFirstRun is better than firstRun.
   • Name functions using verb forms: increment is better than plusOne. unzip is better than filesFromZip.
   • Name event handlers to express when they run. onClick is better than click.
   • Put statements and expressions in positive form.
     • isFlying instead of isNotFlying. late intead of notOnTime.
     • Lead with positive conditionals. Avoid if not something then ... else ... end.

• If we only care about the inverse of a variable, turn it into a positive name. missingValue instead of not hasValue.