Like, use createSuperUser() instead of just createUser(). Also, try to be specific with functions and methods name to give more clarity to the user. Therefore, they should be named by a verb.įor example: validateEmail(), saveUser(), leteUser(), createLog(), etc.īut for scenarios when a function returns a boolean there you can use short phrases with adjectives.įor example: isEmpty(), isPincode(), isValid(), isEmail() etc.ĭon't try to use nouns for function names as it will confuse the reader like email()instead of isEmail(). Functions (and Methods)įunctions and Methods are meant to perform tasks and operations i.e., action. For example, isValid, isPassed, isReal, emailExists, etc. For example product, seller, student, price, user, etc.īut for booleans, you can go for short phrase with an adjective. Mostly you should use nouns for naming variables and properties. Especially in JavaScript, justifying types through naming matters more as JavaScript is value typed not data typed language (In JS, we don't declare type while declaring variables).ĭata stored in variables or properties are of value types - number, string, boolean, array, etc, therefore, name them accordingly. The name of a variable or property should represent the type or any kind of data stored in it. Rules of Naming Variables (and Properties) But when you keep trying to come up with better names in code, you will lean towards perfect. The name should reflect whatever is inside instead of confusing your junior developer.Īlthough you don't start giving perfect names on the first go.

Whatever name you provide to the variable, function, class, etc should describe it well. Good naming of variables, functions, properties, methods, classes, constants, etc makes code more predictable and contributes highly towards clean coding. But that sucks to have to do.If you aren't going to name it better then people aren't going to interpret it better.

If we did it this way, we'd be binding the current value of student to a scope where the reference to student cannot change on each iteration of the loop. Now, not to throw out too much terminology, but closures are IIFEs which will. = We inner-wrap it with a Promise so that the calling function can // = wait for it to be resolved or rejected. = // = In order to make this function asynchronous, we 'promisify' it.

Javascript cleancode