10 Tips Menulis Code JavaScript yang Clean

Summary

In this engaging video, the speaker, Awali, shares essential tips for writing clean JavaScript code. The script begins with an explanation of clean code, emphasizing its importance for readability and maintainability. Awali then presents ten practical tips, such as using English for variable naming, choosing verbs for functions, and plurals for arrays. The tips also cover avoiding ambiguous variable names, simplifying conditions, and ensuring functions have a single responsibility. The video aims to help developers write more understandable and error-free code, with a promise of more tips in a follow-up episode.

Takeaways

• 😀 Clean code is defined as code that is easy to understand and modify by others.
• 📝 Always use English for naming variables, even if the application is in another language.
• 🏷️ Use verbs for function names and nouns for variable names to improve clarity.
• 📚 Use plural forms for array variables to indicate that they contain multiple items.
• 🔄 When iterating over an array, use the singular form of the array's variable name for clarity.
• 🔑 Prefix boolean variables with 'is', 'can', or 'should' to make their purpose clear.
• 🔒 Store conditions in variables to simplify the code and make it more readable.
• 🚫 Avoid using 'not' in variable names as it can make reading the code more difficult.
• 📈 Use specific and explicit names for variables instead of generic terms like 'data'.
• 🔧 Functions should have a single responsibility to make the code easier to understand and maintain.
• ⚙️ Use JavaScript linters to catch and correct inconsistencies in your code, such as formatting errors.

Q & A

What is the definition of 'clean code' according to the video script?

Clean code is defined as code that is easy to understand and modify, similar to how the quality of a sports car can be measured by the number of 'WTFs per minute' - if it's hard for others to understand, it might indicate poor code quality.

What is the first tip shared in the script for writing clean JavaScript code?

The first tip is to always use English for naming variables, regardless of the application's language, to maintain code cleanliness.

Why should verbs be used for functions and nouns for variables according to the script?

Using verbs for functions and nouns for variables helps to clearly distinguish between actions (functions) and data (variables), making the code more readable.

What is the recommendation for naming variables that represent arrays?

The recommendation is to use plural forms for array variables to accurately represent that they contain multiple elements.

Why should the singular form of the variable name be used during iteration over an array?

Using the singular form during iteration helps to clearly indicate the individual elements being processed within the array.

What is the purpose of using prefixes like 'is', 'can', or 'should' for boolean variables?

These prefixes make the purpose of the boolean variable clearer and reduce ambiguity, making the code easier to understand.

Why should conditions be stored in variables?

Storing conditions in variables makes the code more readable, as it allows others to understand the logic without having to parse complex conditional statements.

What is the advice against using the word 'data' when naming variables?

The word 'data' is too generic, and it's advised to use more specific or explicit variable names to represent the actual data being stored.

What is the main reason for keeping functions focused on a single responsibility?

Focusing functions on a single responsibility makes the code easier to understand, maintain, and debug.

Why is it important to use JavaScript linters?

JavaScript linters help identify and correct inconsistencies and errors in the code, promoting a more consistent and clean coding style.

What does the script suggest for those who are not fluent in English when naming variables?

The script suggests using tools like Google Translate to assist with naming variables in English, as it's important for code cleanliness.