# Write Clean Code || Javascript || SOLID Principles Writing clean code is what you must know and do in order to call yourself a professional developer. There is no reasonable excuse for doing anything less than your best. > “Even bad code can function. But if the code isn’t clean, it can bring a development organization to its knees.” — Robert C. Martin (Uncle Bob) Follow Proper Naming convention 1. **camelCase :** Symbols, properties, methods, pipe names, non-component directive selectors, constants uses lowercase on the first letter of the item. For example, “selectedUser” 2\. **UpperCamelCase (or PascalCase):** Class names, including classes that define components, interfaces, NgModules, directives, and pipes uses uppercase on the first letter of the item. 3\. **dash-case (or “kebab-case”):** The descriptive part of file names, component selectors uses dashes between the words. For example, “app-user-list”. 4\. **UPPER\_UNDERSCORE\_CASE:**All constants uses capital letters connected with underscores. For example, “NUMBER\_OF\_USERS”. #### This playlist talks about how you can write clean code in javascript Javascript Writing clean Code || Code Reviews #01 clean Code Variable naming #02 Writing Clean Code for Functions #03 Small functions for Code segregation & unit testing #04 Avoid Side Effects #05 Write Functional Programming #06 Refactor Code with Classes #07 Follow SOLID principles #08 Liskov Substitution Principles #09 Interface Segregation Principles #10 Dependency Inversion Principles #11 Write Clean Code Example #01 #12 Write Clean Code Example #13 Code Example Module Patterns #14 Code Review for writing Javascript Code #15