Hi, I'm Eryn!
- San Francisco
-
14:57
(UTC -07:00)
Highlights
- Pro
Pinned Loading
-
-
Best Practices for Clean Code
Best Practices for Clean Code 11. Use descriptive and obvious names.
2- Don't use abbreviations, use full English words. `player` is better than `plr`.
3- Name things as directly as possible. `wasCalled` is better than `hasBeenCalled`. `notify` is better than `doNotification`.
4- Name booleans as if they are yes or no questions. `isFirstRun` is better than `firstRun`.
5- Name functions using verb forms: `increment` is better than `plusOne`. `unzip` is better than `filesFromZip`.
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.





